6 Sep 96

SUBJECT: USSTRATCOM C4I Systems Migration Strategy

1. PURPOSE: Provide outline on J61's systems migration strategy for Industry Day

2. KEY POINTS:

- Operational Architecture

-- Definition: The descriptions of the tasks, operational elements, and information flows required to accomplish or support a warfighting function (operational concepts and required activities, connectivities, and data flows)

-- We are merging Command Intelligence Architecture Program (CIAP), C4I Master Plan, and requirements documents from individual programs into C4ISR Strategy Summary Document

-- Year 2000 C4I Integration Study Group

--- Cross-directorate group to define and prioritize high-level USSTRATCOM-wide requirements

--- Use Activity Based Costing (ABC) to make business case for changes

--- Perform process reengineering to determine how best to do the job

-- J6 tasks

--- Document "as is" operational architecture (consolidate inputs from each area)

--- Document "to be" operational architecture (based on inputs from study group)

- Technical Architecture

-- Definition: A minimal set of rules governing the arrangement of the parts or elements whose purpose is to ensure that a conformant system satisfies a specified set of requirements (standards profile)

-- J6 tasks

--- Implement standards-based architecture

--- Define common building codes (standards) for USSTRATCOM-based on JTA

--- Define common building blocks (reusable code) starting with the DII COE components

--- Standardize data

PREPARED BY: CAPT M. A. RANDOUR

J614, EXT. 2-3719

APPROVED BY: RADM P. D. MONEYMAKER, J6

CAPT HANSELL, J61

- Systems Architecture

-- Definition: The descriptions, including graphics, of systems and interconnections providing for or supporting warfighting functions (the parts of a system to include their technical characteristics)

-- J6 tasks

--- Define Enterprise database

---- Standard DoD Data Elements

---- Standard ASCII SQL calls

---- Standard DBMS

--- Specify wide and local area networks

--- Implement System Integration Management (SIM) Systems Architecture

---- Document and consolidate "as is" architecture

---- Document and consolidate near-term (1-2 years out) "to be" architecture

-- Networks

--- Document current architecture

--- Analyze new requirements and plan changes to architecture

--- Current Projects

---- DISN LES - bring ATM switch to Offutt

---- DMS

--- Future Project

---- DII replacement for GCCS and DoDIIS

-- Approach

--- Use System Integration Management (SIM) Process to manage migration

--- Use System Integration Management Reviews (SIMRs) to monitor progress

--- Same process as applied in Intel's Architecture 95

--- Reference: DoDIIS SIM Concept of Operations and Handbook

- System Integration Management Process

-- Goals

--- Identify and document operationally relevant systems architecture goals

--- Plan a cost-effective, operationally focused implementation of those goals

--- Execute the transition from existing ("as is") to desired ("to be") baselines

--- Communicate results of analysis, transition status, issues, resolution plans, and recommendations to senior management

- System Integration Management Review

-- USSTRATCOM-level SIMR will tie together reviews of individual programs

-- Conducted monthly

-- Attended by upper management, project action officers, users, operators, maintainers, and developers

-- Information focuses on status of integration capabilities projected for operations over the coming year

- Future Directions

-- Year 2000 C4I Integration Study Group

-- CESAR contract

-- USSTRATCOM-level SIMR