C4I Support Plans (C4ISP) Overview Brief · This briefing entitled "C4I Support Plans (C4ISP)...
Transcript of C4I Support Plans (C4ISP) Overview Brief · This briefing entitled "C4I Support Plans (C4ISP)...
1
C4I Support Plans (C4ISP) Overview Brief
C4I Support Plans (C4ISP) Overview Brief
Keith DeanOASD(C3I) \ C3ISR & Space Systems
(703)[email protected]
http://www.dsc.osd.mil
Joint C4ISR Decision Support Center
Form SF298 Citation Data
Report Date("DD MON YYYY") 01111999
Report TypeN/A
Dates Covered (from... to)("DD MON YYYY")
Title and Subtitle C4I Support Plans Overview Brief
Contract or Grant Number
Program Element Number
Authors Project Number
Task Number
Work Unit Number
Performing Organization Name(s) and Address(es) Information Assurance Technology Analysis Center (IATAC)3190 Fairview Park Drive Falls Church VA 22042
Performing Organization Number(s)
Sponsoring/Monitoring Agency Name(s) and Address(es) Monitoring Agency Acronym
Monitoring Agency Report Number(s)
Distribution/Availability Statement Approved for public release, distribution unlimited
Supplementary Notes
Abstract
Subject Terms
Document Classification unclassified
Classification of SF298 unclassified
Classification of Abstract unclassified
Limitation of Abstract unlimited
Number of Pages 19
REPORT DOCUMENTATION PAGEForm Approved
OMB No. 074-0188Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions,searching existing data sources, gathering and maintaining the data needed, and completing and reviewing this collection of information. Sendcomments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden toWashington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 205031. AGENCY USE ONLY (Leaveblank)
2. REPORT DATE11/1/99
3. REPORT TYPE AND DATES COVEREDBriefing
4. TITLE AND SUBTITLEC4I Support Plans Overview Brief
5. FUNDING NUMBERS
6. AUTHOR(S)Not provided
7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) 8. PERFORMING ORGANIZATION REPORT NUMBER
Information AssuranceTechnology Analysis Center(IATAC)3190 Fairview Park DriveFalls Church, VA 220429. SPONSORING / MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSORING / MONITORING
AGENCY REPORT NUMBER
Defense TechnicalInformation CenterDTIC-AI8725 John J. Kingman Road,Suite 944Ft. Belvoir, VA 2206011. SUPPLEMENTARY NOTES
12a. DISTRIBUTION / AVAILABILITY STATEMENT 12b. DISTRIBUTION CODE
A
13. ABSTRACT (Maximum 200 Words)This briefing entitled "C4I Support Plans (C4ISP) Overview Brief presented by OASD (C3I) \C3ISR & Space Systems, presents the C4ISP as a systematic approach to credibly andaffordably implement information capabilities and identify dependencies, shortfalls, andimpact on C4I infrastructure early on in the acquisition process.
14. SUBJECT TERMSC4I
15. NUMBER OF PAGES
16. PRICE CODE
17. SECURITYCLASSIFICATION OF REPORT
Unclassified
18. SECURITYCLASSIFICATION OF THIS PAGE
Unclassified
19. SECURITY CLASSIFICATION OF ABSTRACT
Unclassified
20. LIMITATION OFABSTRACT
Unlimited
NSN 7540-01-280-5500 Standard Form 298 (Rev. 2-89)Prescribed by ANSI Std. Z39-18298-102
2
Problem StatementProblem StatementProblem Statement
Given:• The Joint Vision 2010 information superiority goal will require a
robust, interoperable and reliable C4I system of systems architecture• Systems will be more dependent than ever on each other to achieve
information superiority• Future military operations portend an increased demand on C4I
support• Current acquisition process must adjustProblem:• A systematic approach is needed to credibly and affordably
implement information capabilities and identify dependencies,shortfalls, and impact on C4I infrastructure early on in the acquisitionprocess
3
BackgroundBackgroundBackground
DOD 5000.1: “Acquisition programs shall be managedto optimize total system performance andminimize the cost of ownership. The total systemincludes ... the operational and supportinfrastructure (including Command, Control,Communications, Computers and Intelligence(C4I).”
DOD 5000.2-R: “A C4I support plan shall be preparedfor all weapons, systems/programs that interface
with C4I systems.” 15 Mar 1996
Acquisition Deskbook: Major updateC4ISP Format Guidance, May 99
CJCS 3170.01: RequirementsGeneration System (formerlyMOP 77) 13 Jun 1997. J-6and DIA are responsible forreviewing and assessingC4ISR requirements and C4Isupport plans.
1-2 QCY/96
3-4QCY/96
1-2QCY/97
3-4QCY/97
1-2QCY/98
3-4QCY/98
1-2QCY/99
3-4QCY/99
USD(A&T), ASD(C3I), VCJCSMemo: DSC et al,develop plans andinstructions for C4ISupport Plans. 16 Jul 97
USD(A&T), USD(C), &ASD(C3I)Memo:Requirements for Compliancewith Reform Legislation forInfo Technology 1 May 1997.Identifies C4ISPs asinformation sources forprogram requirements.
CJCS 6250: Satellite Communications,SATCOM requirements shall beidentified in the C4ISR Support Plans.20 Oct 98.
C4I Support Plan WG:
Stand up of Working Group. Oct 97
CJCS 3170.01: RequirementsGeneration System. C4ISPcoordination process andcontent clarifications,10 Aug 99
4
C4I Support Plan GoalsC4I Support Plan GoalsC4I Support Plan Goals
Program Offices:r Identifies C4I system support needs for weapons, systems/programsr Identifies dependencies between systemsr Identifies interface requirements early-on in acquisition processr Mechanism to identify, plan, and manage implementation issues related to C4I
infrastructure requirementsr Enables trade analysisC4I Support Organizations (interfacing systems, service providers)r Determine if system is supportabler Ensure systems being developed have adequate and sufficient C4I resourcesr Facilitate interoperability , integration & compatibilityJoint Staffr Assist in certification processes (interoperability & intelligence)r Assess impact on C4I infrastructureOSDr Assess compliance with standards, architectures, investment strategyr Identify C4I Support deficienciesr Assess & manage interoperability and integration effortsALLr Raise & resolve issues
5
Game PlanGame PlanGame Plan
p Establish a C4ISP working group to develop theprocess and set of procedures to assist indeveloping C4ISR Support Plans
p Develop an Action Planp Establish C4ISP coordination processp Clarify existing C4ISP guidancep Raise & resolve issues related to fielding systems
with necessary C4I supportp Show immediate value
6
C4ISP WG Primary PlayersC4ISP WG Primary PlayersC4ISP WG Primary Players
Organizations• OSD
4 OASD(C3I)4 OUSD(A&T)
• JS4 J2 (IRCO)4 J6
• Services4 ARMY: DISC44 AF: SAF/AQI, XOR, AFCIC,
497th IG4 NAVY: N6, SPAWAR
• Agencies4 DISA,JITC, JSC4 DIA4 NSA4 NIMA
• Other CAEs• BMDO• NRO
Functions• PSAs• PM
4 JSF PMO
Others as Appropriate
7
MilestonesMilestonesMilestones
NEAR-TERM(0-3 mon)--C3I agreement on C4ISP COA- Coordinate COA w/JS- Establish C4ISP working group- Develop Action Plan
MID-TERM(3-9 mon)- Coordinate Action Plan with Services & Key Players- review current instructions & processes-Propose and prepare updates-Prepare sufficiency checklist-Identify C3I resources and implement procedures-Brief Services/Agencies/PMs on process-Establish C4ISP Helpdesk
LONG-TERM(9-18 mon)-Clarify Guidance-Coordinate and update DoD Regsand DOD and JS Instructions-Develop DSMC curriculum toinstitutionalize process
as of 9 Jan 1998
8
OSD,JS, AgenciesOther SMEsfor analysis
ASD(C3I) MDA
ComponentMDA
C4I Support PlanCoordination CONOPs
C4I Support PlanC4I Support PlanCoordination CONOPsCoordination CONOPs
OSD,JS, AgenciesOther SMEsfor analysis(via working
group)
ASD(C3I)/PA&I
InterfacingProgram
Offices (IPOs)for
requirementsacceptance
PMPEO
Service
Integrated Product TeamFor Plan Development
Formal MilestoneCoordination(NLT 60 days prior to MS)
For ACAT I & IAs, Special Interest Systems
Forward criticalconcerns
Allothers
9
ChallengeChallengeChallenge
Conceptual BreadthDetail Available
“Cost” to Resolve C4I Support Issues
time
MS 0MNS
MS IORD
MS IIEngineering/
Manufacturing
MS IIIProduction/
Fielding
Optimal Zone forIssue Identification
10
Issue Resolution ProcessIssue Resolution ProcessIssue Resolution Process
Review &Analyze Plan
Issues?
N
Y
stop
Document &DetermineResolution
Path
OPTIONS:-PM resolution-Interfacing PM resolution- IIPT/OIPT/DAB-PPBS-JROC/JWCA-MIB/MCEB-Study
11
C4I Support Plan ContentsC4I Support Plan ContentsC4I Support Plan Contents
• Introduction:• High level system description, directory of related information to be exchanged
• System Description:• Detailed overview of the system, including all characteristics relevant to C4I support
• Operational Employment:• Defines employment concept, roles & missions, mission type, employment
rate/requirements, operational architecture view, operational info exchangerequirements, event trace timelines
• Derived C4I Support Requirements• Quantify operational requirements placed on supporting C4I systems• Define systems architecture view and system info exchange requirements• Identify C4I infrastructure necessary for T&E and training
• Potential C4I Support Shortfalls & Proposed Solutions• Operational employment, testing & training support shortfalls• Identify impact of shortfall on operations and propose solution
• Appendix (i.e. ITMRA requirements compliance)
* as per Acquisition Deskbook, dtd May 99
12
C4I SP Architecture FrameworkProducts
C4I SP Architecture FrameworkC4I SP Architecture FrameworkProductsProducts
Darker colors show areas of emphasisLighter colors show support activities
High-Level Activity ModelHierarchical Chart
Employ FirepowerEmploy Firepower
Attack Targets(Execute Mission)
Attack Targets(Execute Mission)
Conduct Targeting(Plan Mission)
Provide ISR
Process, Exploit, & Disseminate Information
CollectInformation
Conduct Strike OperationsConduct Strike Operations
Note: Information on this graphic is NOTIONAL and is intended for illustrative purposes only.
Information Exchange Requirements Matrix
Use Source Information Attributes
ProducingOperationalElement
ConsumingOperationalElement
ActivitySupported
SystemWarfighterInformation
InformationSecurity
Size / Units(optional)
MediaType
Quantity (optional)
Quality (optional)
Timeliness (optional)
UJTL orServiceMission
EssentialTask Code
Could be byInformationElement or
DataElements
Could be byInformationElement or
DataElements
Voice,Video,Data
Frequencyof
exchangesover a
period oftime
AcknowledgeAuthentication
MessageError Rate
PrecedencePerishibility
Modeof
Communication
Note: Information on this graphic is NOTIONAL and is intended for illustrative purposes only.
Current
Planned
P R
NAVY3 1
A, B C
A, B C
Voice( SLOB / RF )
C
SEAD Timeline, min.
Shooter
A, B
TIBS
Shooter
Current RF / SLOB Rng Unknown
TargetingData Provided
ShooterMode
0.50
VoiceXmit
C
8.00
SensorCollect
A
1.50
Sensor Process
B
12.70
Total
1.00
ShooterProcess
F
Planned RF / Lat-Long Rng Known 0 . 13.45 6.251.00
TargetingData Provided
ShooterMode
Joint TIBSCollect / Process TotalTIBS
XmitShooter Process
Precision Strike Timeline, min.
Note: Information on this graphic is NOTIONAL and is intended for illustrative purposes only.
P R
NAVY3 1
TIBS(Location / RF )
D
D
Voice( SLOB / RF )
E
E
F
F
0.50
Process
D
0.50
Combat Direction
1.00
Analyze
1.00
0.20
VoiceXmit
E
0.2
Voice XmitProcess
Combat DirectionAnalyze
Voice( Location / RF )
EFD
G I
CNR(AFATDS) Shooter
HTOC
ASASBN4 pt. fill
GSMBTRY
CNR(AFATDS)
CNR(AFATDS)
Planned Initial Queing Missile X 0.13.45 11.387.00
TargetingData Provided
Weapon Joint TIBSCollect / Process
A
Total
CB DTIBSXmit
ASASProcess
0.01
ECNRXmit
0.30
FBN
Process0.30
HBtry
Process0.01
GCNRXmit
0.01
ICNRXmit
0.20
JMLRSProcess
Target
Sensor to Shooter Event Trace Timeline Example
Sensor
Sensor
MS0 MS I MSII MSIII
OpArchView
SysArchView •Op Concept Diagram
•High-level Activity Model
•Information Exchange Requirements•Op Node Connectivity Diagram•System interface Diagrams
•Event Trace Timeline•Tech Architecture Profile
Systems Interface DiagramDSC/J6 - TAD: CRUISE MISSILE OPSIT
Systems Interface DiagramSystems Interface DiagramDSC/J6 - TAD: CRUISE MISSILE OPSITDSC/J6 - TAD: CRUISE MISSILE OPSIT
G B D L
NTMNTM
Afloat CIC
Command & Control Weapons Platforms
TIBS / IBS
AWACS
Bde ADTOCBn ADTOC
TPS-75(USAF)
F -15
Aegis
F -14, F/A -18
TPS-59(USMC)
CEC
F -22
Patriot PAC-III
Hawk Follow-OnMissile System
FO/LAN
Hawk Follow-OnRadar System
INTER-SERVICELINKS
MPQ-53( Patriot )
Non
Inte
grat
edC
EC
Rel
ay
GBS MPQ-64FAAD
TPQ-36 / 37
H a w kFiring Unit
INTER-SERVICE LINK
Hawk C2
ECS(Firing Unit)
TAOC ( SAAWF )( USMC )
Battle Management
RF
FO
FO
C J T FGCCS
GCCS
JFACCG C C S
AOC
JFMCCG C C S
TFCC
JFLCCG C C S
TOC/COC
RF
COMMONGROUNDSTATION
USNG C C S
TFCC
U S A FGCCS
AOC
USMCGCCS
C O C
USAG C C S
TOC
JFSOCCGCCS
S e n s o r sC4 Improvements
E-2 APS-145 AWACS APY-1
INTRA - SERVICE LINK
U . S . A I R F O R C E
U.S. AIR FORCE
NAVY
NAVYAerostat
LINK-16
ADTOCCRC/CRE(USAF)
TAOC(USMC)
INTRA - SERVICE LINK
ICC
AegisSPY-1
Note: Information on this graphic is NOTIONAL and is intended for illustrative purposes only.
TargetDesignator
PrecisionEngagement
ForwardObserver
HUDTGT & SA Visual / Voice Only
Target Data& Situational
Awareness
Operational Concept DiagramDSC/J6: CAS - Digital vs. Voice - Lethality & Survivability
Operational Concept DiagramOperational Concept DiagramDSC/J6: CAS - Digital vs. Voice - Lethality & SurvivabilityDSC/J6: CAS - Digital vs. Voice - Lethality & Survivability
500
1000
1500
5 0 0
4 5 0
4 0 0
0 8 09 1 0
1 01 0
Note: Information on this graphic is NOTIONAL and is intended for illustrative purposes only.
SOF Recce
CINCJIC JOC
CJTFIntel Ops
Missiles
Forces
Artillery
Ships/Subs
A O C
CTOC
MAGTF COC
Discipline/Service-Specific
ProcessingFacilities
CDC
W O C
AWACS
ABCCC
CG/LHD
FightersSatellite
Airborne
UAV
Ground
Shipboard
National Exploitation
RSOC
SOF HQ SOF Teams
JTAGS
CARS
GSM
IPF
MCSClassified
JMPUDDL/CourierIMETS(Wx) @CTOC,DTOC,ACE
JSTARS
Bombers
DTOC Bde FSE
ACE
GCE
E-2C
Missiles
CRE/CRC
ADA TOCs
Collection, Processing, Assessment Command and Control ExecutionDefense Network
TIB
S/T
RA
P
Tac
tica
lD
ata
Lin
ks RF Data/VoiceOrganic Data Links
MILSTAR, WB-HF, FltSat
FightersCGS
MIES
MIPE
JSIPS
SATCOM
Warning Net
Fighters, AttackAircraft
Operational Node Connectivity Description
Note: Information on this graphic is NOTIONAL and is intended for illustrative purposes only.
13
C4ISP Potential ShortfallsProduct
C4ISP Potential ShortfallsC4ISP Potential ShortfallsProductProduct
Task
INGRESS
Accurate navigation data
Ability to pass datain flight
Ability to receive threat updates in flight
Ability to receive new tgt locn (prec. Coords)
...
ISRSensors
C2 Comm CM PED Nav Log
14
ACAT DistributionACAT DistributionACAT Distribution
3055
85
34 3872
529 529
0
100
200
300
400
500
600
ACAT I ACAT IA ACAT II&III
DAB IT OIPT ComponentSpecial Interest Total
1997 Programs by Acquisition Category
686 Programs:
-- 157 ACAT I and IA
-- 529 ACAT II & III
15
MilestonesMilestonesMilestones• C4ISPs are “living documents”• Updates prior to each milestone decision• Update when program/system upgrades affect or impact C4I
infrastructure
Milestone O:Approval to
ConductConceptStudies
1st Edition
Milestone I:Approval toBegin a NewAcquisition
Program
2nd Edition
Milestone II:Approval to
EnterEngineering &ManufacturingDevelopment
3rd Edition
PM’s submit NLT 60 days prior to Milestone
Decision 30 day approval process
PROPOSED
Upgrade
5th Edition
Service C4ISP officesubmits 30 days priorto decision point for
upgrade
Milestone III:Production or
Fielding/Deployment
Approval
4th Edition
16
. Force XXI Battle Command Brigade & Below(FBCB2), dtd 8/99
. F/A-18 (Strike Fighter), dtd 8/99
. Theater High Altitude Area Defense(THAAD), dtd 7/99
. F-22 Advanced Tactical Fighter , dtd 5/99
. Battlefield Combat ID System (BCIS)dtd 5/99
. Theater Medical Information Program(TMIP) dtd 5/99
. JSTARS Common Ground Station (CGS)dtd 4/99
. Navy Theater Wide BMD dtd 2/99
. Hard & Deeply Buried Target Defeat dtd 1/99
. Advanced EHF MILSATCOM dtd 1/99
. Army Tactical Missile System-BAT dtd 10/98
6/996/97 1/98 6/98 1/99
. Secure Mobile Anti-Jam Reliable TacticalTerminal (SMART-T), dtd 10/98
. Maneuver Control System (MCS), dtd 8/98
. Joint Air to Surface Standoff Missile(JASSM),dtd 8/98
. 21st Century Tactical Aviation SeabasedPlatform (CVX), dtd 5/98
. Joint Strike Fighter (JSF),dtd 3/98
. Joint Precision Approach and LandingSystem (JPALS), dtd 3/98
. Joint Stand Off Weapon (JSOW)
. Patriot System, dtd 5/97
. Theater Missile Defense (TMD), 7/96
C4ISPs ReceivedC4ISPs ReceivedC4ISPs Received
1/00
17
Checks and Promising ToolsChecks and Promising ToolsChecks and Promising Tools
Analysis Needs• System of Systems Check. Can the proposed
system be coherently integrated into the operationaland systems architecture by mission area?
• Interoperability & Compliance Check. Is proposedsystem interoperable w/ interfacing systems? Isproposed system compliant w/ tech standards, ITMRA
• Information Mgmt/Delivery/Dissemination &Sufficiency. Are information timelines adequate? Isthere sufficient information support & resources for thissystem?
• Cross-Program Analysis. Are interfacing programsin synchronization?
• Info Security Check. Are proposed informationsecurity solutions adequate?
• Issue identification and resolution. What C4Isupport issues exist and how can they be resolved ?
Other needs• C4ISP Development
• On-line library & electronic doc coord
Promising Tools• Joint C4I Architecture
Planning System (JCAPS)• Levels of Information
SystemsInteroperability(LISI)
• NETWARS
• PPBS tracker
• Issue Tracking DB
• Joint System RequirementsTracking Tool (JSRT2)
• Info Analysis Program
18
OSD C4I Support Plan Points of Contact
OSD C4I Support PlanOSD C4I Support Plan Points of Contact Points of Contact
OASD(C3I) C4I Support Plans:Mr. John BuchheisterProgram Analysis & Integration DirectorateDASD C3I & Space
Working Group:Keith DeanOASD(C3I)/DSCCrystal Mall Three, Room 60041931 Jefferson Davis HighwayArlington, VA 22202(703) 607-0596, (703) 607-0603 [email protected]
Web site: www.dsc.osd.mil