1. Marine Corps Systems Command PM Communication Systems
CONDOR
BCOTM Brief
Mr. Bart Soucy
August 2004

2. CONDOR “Gateway” EPLRS Community The CONDOR Gateway:
Beyond
Line of Sight
The CONDOR Gateway:
Purpose: Connects EPLRS Communities over distance.
EPLRS Node
C2PC Gateway
Over-the-Horizon connection (INMARSAT, Iridium, TACSAT)

3. CONDOR “PoP-V” EPLRS Community Gateway PoP-V Beyond Line of Sight
INMARSAT
or TACSAT
The CONDOR Point of Presence Vehicle:
Purpose: Connects Users without EPLRS to the TDN
SINCGARS
HaveQuick II
TACSAT DAMA HF
HF ALE
EPLRS
Iridium - ETCS …
PoP-V
Gateway

4. CONDOR “Jump C2” The CONDOR Jump C2 Vehicle:
Purpose: Maintains COP/SA during Displacement
Downsized JECCS Capability
SIPRNet
NIPRNet
Telephone
VTC
Beyond
Line of Sight
UOC
MAIN
Jump
Command Vehicle
INMARSAT
Wireless Technology
Up to 2 miles
CONDOR “Jump C2”

5. US Army & CONDOR
9 June USMC CONDOR Team met with US Army Central Technical Support Facility (CTSF) Staff, Fort Hood, Texas
Two US Army FBCB2 HMMWVS have been shipped to SPAWAR, Charleston for CONDOR Gateway Integration
US Army, USMC, and CenGen will cooperate on US Army to USMC EPLRS issues concerning interoperability to include COP-B
Possible Sea Viking 05 Integration – (MCWL) Develops and assess future Sea Based Marine Expeditionary Brigade (MEB) capability sets, Expeditionary Strike Group/Force (ESG/F) capability sets, and Sea Based C2 capability sets required for joint forcible entry operations.
Trident Warrior 06 (TW-06) Integration – (Navy) Develops both the architecture by which Navy, joint and coalition force systems communicate, and the logistics to support such a network.
COP-B:
Army (PM TRCS)
LtCol Conley – Asked for this in 1st Qtr 04
Mr. Buzz Kowaluk – (732)
Raytheon
Jack O'Connor
Phone
Fax
Cell Phone

6. US Army CONDOR GW
Possible Sea Viking 05 Integration – (MCWL) Develops and assess future Sea Based Marine Expeditionary Brigade (MEB) capability sets, Expeditionary Strike Group/Force (ESG/F) capability sets, and Sea Based C2 capability sets required for joint forcible entry operations.
Trident Warrior 06 (TW-06) Integration – (Navy) Develops both the architecture by which Navy, joint and coalition force systems communicate, and the logistics to support such a network.
COP-B:
Army (PM TRCS)
LtCol Conley – Asked for this in 1st Qtr 04
Mr. Buzz Kowaluk – (732)
Raytheon
Jack O'Connor
Phone
Fax
Cell Phone

7. Transit Case Mounted Components
US Army CONDOR GW
Nomenclature
Model/Part No.
Source
Transit Case Mounted Components
MILEX Transit Case XX
EDAK Inc. (US)
PDU DC to AC Inverter
NCGL1.5k-2U R-7647
Nova Electric
INMARSAT M4 Mobile ISDN
TT-3082A
LandSea Systems, Inc.
In-Line Network Encryptor
Sectéra, KG-235
General Dynamics C4 Systems
Power Supply, DC (KG-235)
Ethernet Router (Red)
CISCO2621XM
Cisco Systems Corp.
Ethernet Router (Black)
CISCO3725
Radio Set, EPLRS
AN/VSQ2C (V) 2
Government Furnished Equipment
USB to 8-Port w/RS232 Adapter
2801
Sealink
Global Positioning System
GPS76
Garmin International Inc.
Power Supply, DC (T-40)
IBM Corporation
Internal Components
Laptop Computer
T-40
Laptop Mount
01008B2230
Diversified Metal Technologies
Equipment Mounting Skid
03005J8100
Laurentide Inc.
Radio Set,
AN/MRC-145A
External Components
Helmet Hard Top
8557-4D-C
AMTECH Corp.
Antenna, VHF
AS-3900
Antenna, EPLRS
AS-3449
Antenna, INMARSAT
TT-3008E
Antenna, GPS
GA-29F
Possible Sea Viking 05 Integration – (MCWL) Develops and assess future Sea Based Marine Expeditionary Brigade (MEB) capability sets, Expeditionary Strike Group/Force (ESG/F) capability sets, and Sea Based C2 capability sets required for joint forcible entry operations.
Trident Warrior 06 (TW-06) Integration – (Navy) Develops both the architecture by which Navy, joint and coalition force systems communicate, and the logistics to support such a network.
COP-B:
Army (PM TRCS)
LtCol Conley – Asked for this in 1st Qtr 04
Mr. Buzz Kowaluk – (732)
Raytheon
Jack O'Connor
Phone
Fax
Cell Phone

8. FY05 Events Development Test and Evaluation: System of Systems Tests
USMC Limited User Evaluation/Subject Matter Expert Demonstration
USMC/US ARMY Limited User Evaluation/Subject Matter Expert Demonstration
Possible Sea Viking ‘05 Integration
Possible Trident Warrior ’05 Integration
Questions?

9. Questions
Questions?

10. Army CONDOR GW
Two CONDOR Gateways to be built, delivered, and integrated at Central Technical Support Facility(CTSF), Fort Hood, Texas
SSCC built CONDOR GW minus Marine Corps EPLRS Transmitter
Army Provided HMMWVs
Army Provided EPLRS Transmitter
Army Provided FBCB2 Terminal

11. Army Configuration Gateway Transit Case
SPAWAR will provide GW with all equipment depicted in green, Army will equip with gear depicted in blue
Cisco 3725
Cisco 2600
KG-235
EPLRS
Bay
“Hardhat”
EPLRS
FBCB2
C2PC
INMARSAT
Power Module
GPS

12. Army Integration Effort
Phase 1: Integrate existing GW configuration with Army EPLRS and FBCB2. Intent is to provide a viable “solution” to address US Army’s EPLRS/FBCB2 extended range requirement.
Beyond
Line of Sight
US Army EPLRS Community
US Army EPLRS Community

13. Army Integration Effort
Phase 2: Integrate existing GW configuration with Army EPLRS and extend “data pipe” from USMC Battalion EPLRS community to US Army Brigade EPLRS community. Intent is to create network extensions to allow TCP/IP communications between two units in a joint environment.
USMC EPLRS Community
Beyond
Line of Sight
US Army EPLRS Community

14. Army Integration Effort
Phase 3: Utilize “data pipe” from USMC Battalion EPLRS community to US Army Brigade EPLRS community to enable passing of Situational Awareness (SA) and Position Location Information (PLI) utilizing each service’s C2 system. Intent is to utilize network extensions to enable C2PC and FBCB2 interoperability.
C2PC
FBCB2
USMC EPLRS Community
Beyond
Line of Sight
US Army EPLRS Community

15. Army Integration Effort
Phase 4: Integration of different EPLRS communities into one GW that accomplishes interoperability piece and allows two units to work side by side with common GW.
C2PC or
FBCB2
Task Force CP
FBCB2
C2PC
US Army Brigade EPLRS Community
USMC Battalion EPLRS Community

16. Assumptions for Phase 1 FBCB2 3.6x with EPLRS 11.3
Planned EPLRS fragmentation – not automatically “self-healing” capability
Only two fragments, and both fragments share the same Bde-wide SA and C2 needlines
If time permits, will relax some of these

17. Scenarios for Phase 1
1-10 Cav unit is well forward of DTAC/4th Brigade, so that it has lost Bde-wide EPLRS connectivity
A company of 1BN22 is well forward of 1BDE and 1BN22, so that it has lost Btn-local and Bde-wide EPLRS connectivity