Information Support Plan (ISP) Paul Szabados [email protected] (703) 607-0246 OASD(NII)/DCIO

Information Support Plan (ISP)Information Support Plan (ISP)

Paul [email protected](703) 607-0246

Paul [email protected](703) 607-0246

OASD(NII)/DCIOOASD(NII)/DCIO

Briefing Overview

• ISP Executive-Level Brief• ISP Executive-Level Brief

• ISP Pilot Program (26 August 2005)• ISP Pilot Program (26 August 2005)

• ISP Enhancement Project (Summer 2006) • ISP Enhancement Project (Summer 2006)

• ISP References and POCs• ISP References and POCs

• Documents transformation toward net-centricity and DoD CIO goals

• Provides for a rigorous IT needs and supportability analysis preventing gaps and lack of capabilities

• Provides evidence and over-sight of system engineering

• Collects DoD information issues

• Provides a resource for cross-program / cross-system analysis

• Used by others:

• J2/J6 for supportability certifications (CJCSI 6212 & CJCSI 3212)• Service Uses such as Gap Analysis• Testing community (JITC Interoperability Certification)• Joint Spectrum Center review and IA status• Study groups (e.g., Joint Forces Interoperability Review Team, Welch Panel, & Joint System Engineering Review Team)• Net-Centric Assessments

Value

JCPAT = Joint C4I Program Assessment ToolJMAAT= Joint Mission Area Analysis Tool

ISP Process

Concept &TechnologyExploration

System Development& Demonstration

Production & Deployment Operations &Support

IOT&EFRP

DecisionReviewA B C IOCIOC FOCFOC

Pre-Systems Acquisition Sustainment

MNS

Block 2

Block 3

AOA

Systems Acquisition(Engineering and Manufacturing Development,

Demonstration, LRIP & Production)

Interoperability Certification TestingC4I and Intelligence Supportability Certification

Prog. Init. ** MS B MS C FRP(As Needed)

ISP Required

Potential Additional ISP Reviews

Blk Upgrades

** Program Init. may precede MS B The Number of reviews of a particular program variesSpace Programs see NS Policy 03-01

* DoD 4630 extends requirements

ISP Relationship to DoD 5000 Acquisition Process

JCPAT-E Tool

JCPAT-E ToolContinued

Chapter 2:Chapter 2:SYSTEM DESCRIPTIONSYSTEM DESCRIPTION

Chapter 3:Chapter 3:OPERATIONAL EMPLOYMENTOPERATIONAL EMPLOYMENT

Chapter 4:Chapter 4:DERIVED C4I SUPPORT DERIVED C4I SUPPORT

REQUIREMENTSREQUIREMENTS

Chapter 5:Chapter 5:POTENTIAL C4I SHORTFALLS & POTENTIAL C4I SHORTFALLS &

PROPOSED SOLUTIONSPROPOSED SOLUTIONS

Chapter 1:Chapter 1:INTRODUCTIONINTRODUCTION

Provides an introduction and acquisition status

Identifies high-level information about the systembeing acquired

Identifies operational and architectural information

Provides analysis and analysis results that identify C4ISR and IT/NSS support requirements

Identifies shortfalls in available or projectedC4I support and interoperability

Note: Supporting appendices provide amplifying data

C4ISP ISP

Chapter 1:Chapter 1:

Program InformationProgram Information


AnalysisAnalysis


IssuesIssues

Note: Supporting appendices provide amplifying data andAdditional architecture views

ISP Content

Step 1: Identify the warfighting missions (or functions within the enterprise business domains)

Step 2: Identify information needed to support operational/ functional capabilities for each warfighting mission identified in step 1 Step 3: Determine the operational users and notional suppliers of the information needed

Step 4: Establish the quality of the data needed to support the functions identified in the programs integrated architecture. Step 5: Determine if timeliness criteria exist for the information. Step 6: Determine / Estimate the quantity of information of each type that is needed. Step 7: Discuss how the information will be accessed or discovered. Step 8. Assess the ability of supporting systems to supply the necessary information. Step 9. Discuss RF Spectrum needs. Step 10. Perform a Net-Centric Assessment. (Network-Centric Checklist) Step 11 Discuss the program’s inconsistencies with the GIG Integrated Architecture and its strategy

for getting into alignment. Step 12. Discuss the program’s Information Assurance strategy and reference the Program Protection Plan. Step 13. Identify Information support needs to support development, testing and training.

ISP Analysis Steps

Precepts and assumptions

Precepts and assumptions

Correlated activities

Correlated activities

AV-1

Correlated systems functions

Correlated systems functions

OV-6c

SV-5

SV-4

OV-5OV-4 OV-2

Overview and Summary Information

Organizational Relationships

Operational Activity Model

Operational Node Connectivity

Operational Activity to Systems Function Traceability Matrix

Systems Functionality Description

Operational Event-Trace Description

Nodes mapped to lifelines

Nodes mapped to lifelines

Nodes participating in operational activities

Nodes participating in operational activities

Activity hierarchy and process flow

Activity hierarchy and process flow

SV-6

Systems Data Exchange Matrix

Operational capability to required system correlation

Operational capability to required system correlation

TV-1Technical Standards

Profile

Applicable standards for a

given architecture

Applicable standards for a

given architecture

OV-1 SV-1

High-Level Operational

Concept Graphic

Systems Interface Description

High-Level OverviewHigh-Level Overview

OV-1 SV-1

High-Level Operational

Concept Graphic

Systems Interface Description

High-Level OverviewHigh-Level Overview

ISP Architecture Views

ISP Architecture Analysis

ISP Dependency Analysis

• Signature data

• Levels of specificity

• Specific data format

• Format of location data

• CEP or Linear EP

ISP Analysis Considerations

• Targeting Support

• Geospatial Information

• Mission Planning

• Intelligence Quality / Quantity

– IMINT

– SIGINT

– MASINT

• Computer Resources

ISP Analysis ConsiderationsContinued

• Transport mechanism (Radio, Satellite, Relay, etc.)

• Networks details (TCP/IP, sub-nets) -- in place (current) and

future (LAN, WAN, CENTRIX)

• Frequency, Spectrum, Timeliness, QOS, and Bandwidth

• Databases

• Software Applications

• Critical interfaces

• Connectivity of joint assets

• Data attributes (tagging, form, processing)

• Information assurance

• Complimentary systems

ISP Analysis ConsiderationsContinued

Operational Issues

Mission

Functional Capabilities impacted

Issue number Supporting system

Issue Issue Description

Issue Impact

Mitigation Strategy/Resolution Path (and Time- Frame)

Development Issues

Testing Issues

Training Issues

Issues

Four elements of the NR Key Performance Parameters (KPP):

• Compliance with NCOW Reference Model

• Compliance with GIG KIPs

• Compliance with DoD Information Assurance (IA) Policy

• Required Integrated Architecture Products

Net Ready KPP

Max number of interfaces = n,where n = number of systems

Net-Centric Enterprise

Information Environment

Max number of interfaces = n(n-1),where n = number of systems

Interoperability KPP ---- Net Ready KPP

Net Ready KPP Thinking

• Net-Centric Operations Warfare (NCOW) Reference Model

Net-Ready Key Performance Parameters (KPP) Parts

• Key Interface Profiles (KIPs)

• Information Assurance (IA)

• Integrated Architecture

• Net-Centric Operations Warfare (NCOW) Reference Model

ResourceService Requests

Interact With NCEnterprise Services

Perform NCUser/Entity Services

Provide NCServices

Manage NCInfo Environment

• Net-Centric Operations Warfare (NCOW) Reference ModelContinued

Program manager compliance with the NCOW RM* is demonstrated through inspection and analysis of a capability's:

• Use of NCOW RM definitions and vocabulary;

• Incorporation of NCOW RM Operational View capabilities and services in the materiel solution;

• Incorporation of NCOW RM Technical View Information Technology and National Security Systems standards in the Technical View products developed

for the materiel solution.

* See DAG, Section 7.2.6 for a description of how program managers show compliance with the NCOW RM. In addition, CJCS Instruction 3170.01 and CJCS Instruction 6212.01 for detailed discussions of the inspection and analysis processes

• Net-Centric Operations Warfare (NCOW) Reference Model Continued

• Key Interface Profiles (KIPs)

Applications to COE/CCP11.

Client to Server10.

Application Server to Database Server9.

Computing KIPs

Secure Enclave Service Delivery Node (e.g., SCI/Collateral KIP)8.

DISN Service Delivery Node7.

Joint Interconnection Service 6.

Teleport (i.e., deployed interface to DISN)5.

JTF Component to JTF Headquarters4.

JTF to Coalition3.

Space to Terrestrial Interface 2.

Logical Networks to DISN Transport Backbone 1.

CommunicationsKIPs


Client to Server10.


Computing KIPs






JTF to Coalition3.



CommunicationsKIPs

Application Server to Shared Data - FIOP (SADI)17.

Applications

Information Servers to IDM Infrastructure16.

IDM to Distribution Infrastructure15.

Management Systems to Managed Systems14.

Management Systems to (integrated) Management Systems13.

End System to PKI12.

Network Operations KIPs


Applications








Client to Server10.


Computing KIPs






JTF to Coalition3.



CommunicationsKIPs


Client to Server10.


Computing KIPs






JTF to Coalition3.



CommunicationsKIPs


Client to Server10.


Computing KIPs






JTF to Coalition3.



CommunicationsKIPs


Client to Server10.


Computing KIPs






JTF to Coalition3.



CommunicationsKIPs


Applications








Applications







(NCES/GES)

Identify Applicable KIPs

For those that apply:

• Have applicable Key Interface Profiles definitions been included as part of the KIP compliance declaration (in CDD)?

• Are the information technology standards for each applicable KIP technical view included in the draft TV-1 for the specific Joint integrated architecture (in ISP)?

• Are the appropriate KIP test procedures addressed as part of the requirement for interoperability system testing and certification (in TEMP)?

• Key Interface Profiles (KIPs)Continued

InterimTeleport

L-BandL

EHF(Adv EHF)

EHF

SHF

KaKa

UHF setAdvanced UHFUHF

CSCI

C-Band

Ku-Band

SHF

X

C

Ku

X

TELEPORT

STEP

Standardized

Interface:Modem ConversionsCryptoSwitching / Routing

DISN Services

Legacy C4I

KIP ScopeGIG Teleport KIP

• Key Interface Profiles (KIPs)Continued

• Information Assurance (IA)

Comply with established accreditation and connection approval processes required for all DoD information systems (DITSCAP*).

• List accreditation documentation (System Security Authorization Agreement – SSAA)• Identify the Designated Approval Authority (DAA) or DISN DAA• Reference your Program Protection Plan• GIG IA Architecture (as appropriate)

* In accordance with DoD Directive 8500.1, all acquisitions of AISs (to include MAIS), outsourced IT-based processes, and platforms or weapon systems with connections to the GIG must be certified and accredited in accordance with DoD Instruction 5200.40, DoD Information Technology Security Certification and Accreditation Process (DITSCAP) .

• Information Assurance (IA)Continued

http://www.dtic.mil/whs/directives/corres/pdf2/d85001p.pdf

DocumentMission

Need

SSAA

Registration Negotiation

CertificationAnalysis

SystemDevelopment

Activity

SSAA

SystemOperation

SSAA

DevelopRecommend.

CertificationEvaluationOf Int Sys

SSAA

AccreditationGranted

CertifySystem

ChangeRequested

ComplianceValidationRequired

Acceptable

Agreement

Ready To

Certify

Phase 1 Definition

Phase 3 Validation

Phase 2 Verification

Phase 4 Post Accreditation

Life Cycle Activity

CorrectNo Yes

YesYes

NoNoReanalysis

No

NoNo

Yes

Yes

Yes

Yes

DITSCAP Process

• Information Assurance (IA)Continued

• Integrated Architecture

Operational

Syst

ems

Technical

• Integrated ArchitectureContinued

DoD Architecture Framework(DoDAF)

Issue IdentificationIssue Identificationand Statusand Status

JMAAT Tool

ISP Pilot Program

ACAT II and belowAnd Non-ACAT

AV-1OV-1 (opt)OV-5OV-6C (opt)SV-1 (opt)SV-5SV-6TV-1

ISP Review Process

Stage I: O-6 Level Review (35 days)Stage II: Flag Level Review (30 days)Stage III: Final Plan (10days)

Current3 cycles at both MS B and MS C

New

MS B (Prog. Init.) (30 days)Pre-CDR (30 days)Final Pre-MS C (10days)

Once per milestone cycle

Pre-Systems Acquisition Systems Acquisition Sustainment

Program Milestones

Space ProgramsProgram Milestones

Initial CapabilitiesDocument (ICD)

Capability DevelopmentDocument (CCD)

Capability ProductionDocument (CPD)

JCIDSProcess

MS A MS B MS C IOC MS B Next Increment

PDR CDR FRPDR

ISP Events

Initial ISP

Revised ISP

ISP of Record

Updated ISP

KDP A KDP B KDP C Final Build Approval KDP B Next Increment

Initial ISPRevised ISP

ISP of RecordUpdated ISP

• Submit Initial ISP• OSD 30 Day Review• Comment Adjudication to OSD• Results feed into PDR• Posted to OSD JCPAT

• Submit Revised ISP• OSD 30 Day Review• Comment Adjudication to OSD• Results feed into CDR• Posted to OSD• JCPAT

• Component Approval• ISP of record• Posted to OSD JCPAT

• Submit Revised ISP• OSD 30 Day review• Comment Adjudication to OSD

Next Increment

ISP Pilot Program

ISP Enhancement Project

ISP Enhancement Project is an on-going development leading to delivery in Summer 2006.

ISP Version 1.0 is the automated Net-Centric process for producing, reviewing, and leveraging Information Support Plans using XML technology.

The improved process will eventually leverage information from the Net-Centricity Knowledge and Assessment Service (NKAS) for net-centric assessments.

Overview

• Improve integration and interoperability of information to support the warfighter and DoD through Net-Centric solutions

• Improve collaboration and information sharing throughout the department on program issues (searchable and discoverable) and will improve ability to assess Net-Centric compliance (Streamlined schedule; Improved performance)

• Provide ready access to issues pertaining to IIPTs, OIPTs, Acquisition boards, DAES, JROCs and other associated forum. (Improved performance)

• Benefit DoD by shortening the development cycle of the ISP, while retaining stringent requirements for analysis (Cost savings)

• Allow disparate programs and PMs to securely share existing architecture products (Streamlined schedule; Improved performance; Cost savings)

• Allow all PMs to leverage existing architectures into new initiatives (Cost savings)

• Provide a methodology for cross-program analysis and is in compliance with the Net-Centric Data Strategy (Improved performance)

Objectives

• Developers can post anywhere within security and control constraints

• Only Handle Information Once (NIPRNET/SIPRNET)

• Process is compliant with the Net-Centric Data Strategy– Visible, available, usable– Tagged– Posted to shared spaces– Enabling many-to-many exchanges

• Version Control of ISP Documents– During development– After it is published

• Constraints– IA rules– Searching NIPRNET for information residing on SIPRNET?

Capabilities

• Who are the Stakeholders?

– ISP developers, ISP reviewers, PMs, PEOs, Agencies and DoD Organizations (Over 200 Users)

– Sent to over 50 Individual Stakeholders for their review & comments (i.e. The Joint Staff, AT&L, JFCOM, Service Headquarters, Service SYSCOMs, Intelligence Communities,…

– Comments are being adjudicated by the project team– Accepted recommendations will be incorporated into the Vision Document and

Requirements Document– A Summary of adjudicated comments will be sent to the Stakeholders

– Sample of initial responses– Stakeholders have expressed positive support to update the process and supporting

system– Stakeholders have indicated a need for ISP training– Stakeholders are interested in sharing ISP data and artifacts– Stakeholders see the ISP project saving time and money

Stakeholders

ISP Developer

Project files

XML Template

XML Schema

ISP(XML doc)

ISP File Server(Service-owned)

RepositoryInterface

Repository

XSLData InputStylesheet

Download

Informal Review

Metadata linked between repository and server

}OSD Provided

}PM Provided

}

OSD Provided

}

ISP Owner

Formal Review

Validationof ISP info

Validationof ISP info

ISP Info ISP Info

ISP Info

Altova© Authentic® interface

}

One-timeInstallation process

ProgrammaticInfo

ExternalAnalysis

Architecture Info

Inputs

CD

Repository, JCPAT-E, or JMAAT website

Request

DOWNLOAD USE TOOL (WEB SERVICE) OUTPUT STORE/POST FOR USE

XML Tagged

Metadata File

Tagged Metadata

}

OSD Provided

Service-owned file server or other

repository?

Input Process

ISP File Server(Service-owned)

Repository

XSLPrint

Stylesheet

Altova© Authentic® interface

User’s PC

ISP(XML doc)

ISP(XML doc)

Download

Download

Printer

JCPAT-E

Comments

ISP Document

}

OSD Provided

}

OSD Provided

}

ISP Owner }

PM Provided

Web Browser

Project files

Download

CDRepository, JCPAT-E, or JMAAT website

Request

SEARCH/LOCATE EXTRACTUSE TOOL FORMAT

(WEB SERVICE) OUTPUT USE DATA

DownloadUnzip andInstall files

View DocumentOnline

Print

Output Process

XML Views

A knowledge and assessment tool is envisioned to tie together the Net-Centric strategy areas, NCOW-RM content, and other authoritative sources

NKAS Collaboration Service

- Defense Acquisition University- National Defense University- External University Support

TransportInformation Assurance

Computing

Data StrategyNet-Centric Strategy Areas

Spectrum Management

Enterprise Services

Sample Artifacts- ICDs, CPDs- CDDs, ISPs

TrainingModules

NKAS

DoD Policies, Guidance andInstruction

Education Assessments

DoD Instruction 4630.8

DoD DecisionSupport Systems

Net-CentricChecklist

NCOW-RM

NR-KPPs

NCOW Sample Templates

NKAS

• Complete Development

• Run Pilot Program– Provide CD to PMs, reviewers, ISP developers, and other users– Installation help will be available for users– Collect feedback and make modifications as required

• Deployment– Provide CD to PMs, reviewers, ISP developers, and other potential users– Files are available on DOD repositories (JCPAT-E, DARS, etc.)– Installation help will be posted for all users

• Policy and Governance recommended changes – Defense Acquisition Guidebook DOD 5000.1/DOD 5000.2– DODI 4630.8, CJCSI 6212, CJCSI 3170.01D, etc.– JCPAT-E and DARS user guides

• Training– Embedded training in download package– Contractor supported training

• Complete development with any changes following the demonstration

Remaining Tasks

ISP References and POCs

1. (Build) Make information available on a network that people depend on and trust

2. (Populate) the network with new, dynamic sources of information to defeat the enemy

3. (Protect) Deny the enemy advantages and expoit weaknesses

DoD Net-Centric Goals

Net-Centric Attributes• Internet Protocol (IP) Based• Secure and Available• Only Handle Information Once (OHIO)• Smart Pull vice Smart Push• Data Centric• Quality of Service (QoS)• Application Diversity• Assured Sharing• Ubiquitous Connectivity

DoDD 5000.1 and DoDI 5000.2, Operation of the Defense Acquisition System

DoD Directive 4630.5 and DoD Instruction 4630.8 Interoperability and Supportability of IT and NSS

DoDI 8320.2 Data Sharing in a Net-Centric DoD

DoD Net-Centric Data Strategy, May 9,2003

Net-Centric Checklist, v 2.1.4, OSD(NII)

DAU Acquisition Guidebook

JROCM, 236-03, 19 Dec 2003, Policy for Updating Capabilities Documents to Incorporate the Net Ready Key Performance Parameter (NR-KPP)

CJCSI 3170.01D, “Joint Capabilities Integration and Development Systems”

CJCSI 3312.01

CJCSI 6212.01C, 20 November 2003, “Interoperability and Supportability of Information Technology and National Security Systems.”

National Space Policy 03-01

DoD Architecture Framework V1.0

ISP References

Mr. Paul Szabados (Land, Space, Intelligence) (703) 607-0246Mr. Carl Little (Air, PGMs, C2) (703) 607-0510Mr. Roger Thorstenson (Maritime and Missile Defense)

(703) 607-0506Mr. Bill Barlow (IT Systems) (703) 607-0490Mr. John Feldman (Select Programs) (703) 607-5420

Web SitesWeb Sites NIPRNETNIPRNET SIPRNETSIPRNET DISA’s JCPATDISA’s JCPAT http://jcpat.ncr.disa.mil http:// jcpat.ncr.disa.smil.mil NII’s JMAATNII’s JMAAT http://www.dsc.osd.smil.mil/pai/index.htm DAU http://akss.dau.mil/DAG/ DSC http://www.dsc.osd.mil/ DoD Enterprise Architecture https://pais.osd.mil/enterprisearchitectures

ISP References available at DSC Website: NIPRNET at http://www.dsc.osd.mil/resources/index.htm

ISP Points-of-Contact