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: 1^st 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:
(a) ARMS: CAMPS' Air Refueling Management System (ARMS) is a web-based application that enables the real-time management of Air Refueling requests within one application. The ARMS application provides a single source of information for both long range and short notice Air Refueling requests, from unit level through the air refueling request validators, to the TACC for appropriate action. ARMS is the integration of many legacy CMARPS subcomponents, to include Receiver Integrated Planning System 2 (RIPS2), Tanker Integrated Planning System 2 (TIPS2), On-Line Trader (OLT), and HORSEBLANKET. These components were part of the 'Long-Range' air refueling planning process. ARMS also integrates the Electronic Air Refueling (A/R) Request System (EARRS), a 'short-notice' A/R request/coordination processing tool. Electronic-mail (e-mail) is the primary method of communicating a changing status in the A/R request and planning system. ARMS will also permit the tracking of annual air refueling allocation and utilization levels by Service or DoD component for improved tanker resource management. ARMS can be accessed at: https://w2kweb1.scott.af.mil/ARMS/
(b) The HORSEBLANKET process supports long-range quarterly tanker allocation scheduling. The Horseblanket process begins with receiver and tanker unit inputs to HQ AMC. Using ARMS, worldwide receiver units submit their formatted air refueling requests, and tanker units provide HQ AMC with their daily support capability. (The legacy RIPS2 and TIPS2 functions may be used for request/capability submittal until the full implementation of ARMS is completed.) While honoring a receiver unit's pre-coordinated refueling requests, ARMS determines tanker capabilities, schedules tankers to support unmatched requirements, and populates the CAMPS database. ARMS then provides all units with interactive "on-line trading" capability, which permits receiver and tanker units to perform last minute additions and modifications to the quarterly schedules. Tanker units use on-line trading to 'sell' and 'buy' air refueling missions - commonly known as "horse trading."
(c) The legacy CMARPS capabilities provide an integrated set of tools to aid mission planners to develop aircraft deployment and employment missions, and solve the air refueling problem of "when, where, and how much". CMARPS functionality was migrated to CAMPS, and is accessed through the CITRIX Metaframe. CMARPS may also be operated in a stand-alone mode on a Sun platform.
(d) ADIS: Aircraft Delivery Information System (ADIS) is an integrated set of automated tools designed to assist the Air Combat Command (ACC) Air Operations Squadron (AOS) Aircraft Delivery Flight (AOD) in planning, controlling, and documenting the delivery of various aircraft to worldwide locations. ADIS stores all data related to an aircraft delivery, generates a suspense for publishing Air Tasking Orders (ATO), and accesses flight profiles. It provides online status monitoring and updating capability for command and control of multiple missions. ADIS produces mission suspense, schedule, and history reports.
(e) TSSAS: TPFDD Sizing, Sourcing, and Analysis System (TSSAS) supports TPFDD analysis, updating, and modification, and provides the capability to determine and source AMC deployment flow support requirements. TSSAS is able to analyze, edit and update TPFDD records, and convert a TPFDD into both airlift and tanker scheduler-compatible input formats. TSSAS provides the capability to analyze, size, and generate mission support forces based on airlift flow planning and supporting tanker schedules. Additionally, TSSAS gives the planner the capability to source the required support for the generated requirements. TSSAS has been enhanced with two initiatives demonstrated during Joint Expeditionary Force Experiments (JEFX) in 1999 and 2000: TPFDD In-An-Hour (TIAH) and TIAH+. They provide three key capabilities: (1) automates more of the functional manager portion of the TPFDD generation process, (2) permits functional managers to build simultaneously a TPFDD via the web, and (3) provides an electronic Joint Operation Planning and Execution System (JOPES) interface that enables direct access to and updating of a TPFDD.
(f) CMARP: The Contingency Mating and Ranging Program (CMARP) determines refueling support for a single cell of aircraft by optimizing refueling locations while maintaining missed refueling recovery capability and minimizing the use of tanker air frames and flight times. CMARP performs aircraft routing and automatically avoids designated restricted areas. The program determines tanker capabilities and assigns tanker support after performing flight simulation for both the receiver and the tanker aircraft. CMARP can generate real time winded flight plans for receivers and tankers and generates textual and graphical summaries for solution analysis.
(g) MSED: Mission Editor (MSED) is a companion program to CAMPS/CMARP which allows Delivery Control Officers (DCOs) to make minor changes to flight profiles, provide input to the Portable Flight Planning System (PFPS), and produce mission paperwork.
(h) TMARP: The Tanker Mating and Ranging Program (TMARP) determines refueling support for multiple receiver missions and schedules the receiver movement according to tanker and crew availability. There are two major components of TMARP. (1) TMARP's Deployment component handles forces that are sized for major regional conflicts. The Deployment component determines support based on tanker aircraft and crew capabilities and restrictions. If a planner is not sure of the best tanker basing options, TMARP can provide a good estimate for optimum basing. (2) TMARP's Employment Mating and Ranging Program (EMARP) determines refueling support for multiple refueling requests, such as a daily ATO, and schedules refueling support for receiver missions subject to tanker availability.
(i) GSICS: The Graphically Supported Interactive Control System (GSICS) provides graphic support and the man/machine interface to the other components of legacy CMARPS, allows interactive data set-up, graphically displays input and output data, and manages planner data files.
------------------------
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), 11^th 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 2^nd qtr FY 98. MEF IAS fielded to II MEF 4^th Quarter FY 98. Units to be fielded to I and III MEF 2^nd QTR FY 99. The IOW Workstations IOC is 1^st QTR FY 99 with FOC in the 2^nd 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: