Systems Systems Systems Integration Systems Integration Systems - - PowerPoint PPT Presentation

Systems Systems Integration ntegration in in an an Systems Systems Integration ntegration in in an an Systems Systems Integration Integration in in an an Operational Environment Operational Environment Systems Systems Integration Integration in in an an Operational Environment Operational Environment

f h l h l f h l h l …or service …or service after ter the sa e sale. e. …or service …or service after ter the sa e sale. e.

Brief to INCOSE Region II Brief to INCOSE Region II

3/5/2013 3/5/2013

LtCol Brandon Johnson LtCol Brandon Johnson Director Director Operating Forces Support Division Operating Forces Support Division 18 November 2006 18 November 2006 18 November 2006 18 November 2006

Overview

• Intro
• Our Mission
• Systems Engineering in DoD
• Systems Engineering in DoD
• The Challenges
• GSWAN – An Example
• Summary

MCTSSA Mission

• To provide technical support to the Commanding

p pp g General, MARCORSYSCOM, and Program Managers to acquire and sustain C4ISR products for the Operating Forces Forces.

• To provide technical support to the Deputy Commander

for C4I Integration MARCORSYSCOM for C4ISR for C4I Integration, MARCORSYSCOM, for C4ISR systems engineering and systems integration.

• To provide a Systems Integration Environment.
• p ov de a Syste

s teg at o v o e t.

• To provide technical support to the Operating Forces for

fielded tactical C4ISR systems. y

System Engineering in DoD

D O T

Training and Education Command Marine Corps Combat Development Command

T M L

Marine Corps Systems Command (Acquisition) Commandant Training and Education Command

L P F

Commandant Installations and Logistics Manpower and Reserve Affairs

• DoD acquisition mandates use of systems engineering (DoD

instructions 5000 1 and 5000 2) and systems engineering includes all

F

instructions 5000.1 and 5000.2), and systems engineering includes all

• f DOTMLPF…but systems engineers generally have limited trade

space outside the “M”.

“System” Complexity is increasing period

C4I Integration Attributes

• “System” Complexity is increasing…period
• Hardware, software
• Process complexity
• Process complexity
• Integration has become a continuous process
• The tsunami of new systems fielded to warfighter forces integration
• The tsunami of new systems fielded to warfighter forces integration.
• Systems of systems, Federations of systems, Families of systems
• Nobody owns the whole “system”

Nobody owns the whole system

• System engineer of System A unaware of System B.
• System Engineering compromises made up front

y g g p p

• Resources are always limited…perfect integration isn’t possible
• Legacy systems and processes are a driver

Legacy systems and processes are a driver

Hardware Complexity

Typical Battalion comms - Iraq yp q Receiver - Transmitter, Radio RT-246/VRC State of the art – Vietnam war

Software Complexity

Process Complexity

Joint Force Functional Commander

CINC CINC

DJFLCC DJFLCC

JFLCC JFLCC

COM AFFOR COM NAVFOR COM COM MARFOR MARFOR COM COM ARFOR ARFOR

ARMY ARMY Force Force MAGTF MAGTF

Taken from a 72 slide brief explaining “ O CO

8

Force Force

“componency” by MARFORCOM.

System of Systems Complexity Models can be useful…but reality is a reality is a little more complex than h h shown here

Support Center Trouble Tickets

272 926 986 1245 408 940 1109 1,328

2004 2005

Total: 3785 Total: 3429

312 588 1355 1259

2003 2004

Total: 3514

180 189 542 760 230 309 990 1173

2002

Total: 1671 Total: 2702

180 189 542 760

500 1000 1500 2000 2500 3000 3500 4000 2001 Hardware Others Software Training/Documentation

Total: 1671

Training / Documentation Tickets Created by system (Top 5)

2001 2002 2003 2004 2005 GCCS 167 GCCS 289 GCCS 338 GCCS 280 GCCS 294 IOS V2 97 C2PC 178 C2PC 221 C2PC 194 C2PC 184 C2PC 96 NETWORK 86 IOS V2 99 TDMS 123 IOS V2 120 NETWORK 58 IOS V2 85 JWARN 98 JWARN 87 NETWORK 103 JWARN 45 IOW 56 NETWORK 72 IOS V2 65 TDMS 95

Tactical C4I Integration Challenges

• Systems integration in an Operational Environment is uniquely

challenging

• Operational Environment in DoD = combat
• Enterprise scale systems (system of systems) located in remote

locations

• Dynamic environment
• No single owner of the system-of-systems
• As much integration done prior to deployment as possible
• So…the new “system” was designed using systems engineering (DoD

mandated)…but now it gets integrated in an Operational “system of systems”. How does that work?

An Operational Integration Example: GSWAN General Storage Wide Area Network (GSWAN)

• I MEF UUNS ~ Oct 2004
• Push UAV video

around battlefield assist around battlefield, assist with IED problem

• VSWAN – Video Storage

Wide Area Network

• Rapid fielding – integrated

under operational conditions.

• Highly successful –

spawned other SWANs: Logistics, HOA, General, MEU MEU.

GSWAN System Description GSWAN System Description



The major functional groups: K B d V S ll A t

 Ku-Band Very Small Aperture

Terminal (VSAT) auto-acquiring antenna, Vi S t Li k IP d

 ViaSat Linkway IP modem,

routers, accelerators, KG- 175/TACLANE, and Cisco Call Manager for SIPRNET Voice g

• ver Internet Protocol (Secure

VoIP). NIPRNET VoIP ready.



All equipment is packaged in g transit cases which are all HMMWV transportable.



GSWAN remotes hub back to the DKET LT at Al Asad.

An Operational Integration Example: SWAN

• Integration Challenges
• Physical
• Placement / Ownership
• Form factor
• Process
• TTPs changed
• Training
• Logical (configuration)

GSWAN fielding team – Iraq

• Proprietary issues
• CDP
• Organizational challenges

Logical Integration

V IP h VoIP phones to CCM routing

VLAN 12

Proprietary Considerations

Benefit: This solution allows 2 devices on single physical port (2 VLANs). Mixing of DHCP and static IP. Consideration: No mixing of non-Cisco IP phones. Consideration: No mixing of non Cisco IP phones.

11th MEU JTF Enabler Physical Integration Challenge 11th MEU JTF Enabler

Developed Independently

MEU – Marine Expeditionary Unit JTF – Joint Task Force DSID – Deployed Security Interdiction Device

Eight routers!

p y y UOC – Unit Operations Center DDS – Data Distribution System MSWAN – MEU Storage Wide Area Network TPFDD – Time Phased Force Deployment Data

g

• u e s

Each “system” also has servers TPFDD Hasn’t changed for MEU Comms – footprint is bigger

Integration is mission effective…but not perfect

Final Thoughts

• Perfect integration is not the goal…mission effectiveness is.
• Human systems integration is critical (effectiveness depends
• Human systems integration is critical (effectiveness depends
• n people’s capabilities, training, currency, proficiency, etc)
• Integration is facilitated by open architecture (OA), non-

Integration is facilitated by open architecture (OA), non proprietary solutions, adaptability (think - internet protocols), simplicity (Occam’s razor)

• “System of systems” integration…still requires systems

engineering discipline

• There’s always factors not considered
• Systems Engineers are the “first line of defense” in solving

system of systems integration problems in the operational environment

QUESTIONS ?

Backup Slides

Wireless Point-to-Point Link (WPPL)

• Orthogonal Frequency Division Multiplexing Waveform (form of

802.16 – WiMax)

• AN-50e system operates in the license-exempt 5.8 GHz band or 5.4

GHz band.

• Delivers rates up to 48 Mbps depending on distance and terrain.
• The essence of OFDM is that it breaks up the transmitted signal into

many smaller signals.

• OFDM can communicate over hills, around buildings, and through

f li f i h bili trees for a non line-of-sight capability.

– NIPRNET and SIPRNET – 4 Voice calls (support POTS, STU/STE, and VoIP phones) 1x1 foot and 2x2 foot antennas – 1x1 foot and 2x2 foot antennas – 10 foot masts