Transcript HF Status Briefing - Morgan State University

Horizontal Fusion
Implementation of a Services Oriented Architecture
Marian Cherry
HF Portfolio Manager
703/607-0234
[email protected]
What is a Services
Oriented Architecture
• A Framework for interoperability that is:
 A Design for an environment that:
– is made up of applications, data, and tools (called
“services”)
• Where the services are:
 distributed throughout the network
– Location is irrelevant
 defined/described using a common language and put in
a registry (much like the yellow pages)
 independent of whatever communications they are
traveling on
 platform independent
• And once discovered:
 they can be retrieved/pulled to the user
 are combined to perform functions
– “Composeable” applications and data
UNCLASSIFIED
Page 2
What is Horizontal Fusion?
• An accelerant for the operational implementation of the GIG
Services Oriented Architecture (framework for interoperability)
 Provide funds to Programs of Record to modify their operational
baselines to join the SOA
– “web”front ends/data labeling/security, etc…
 Maximize ROI of legacy investments
– Modify vs. rebuild
– Capitalize on existing training
• A Pathfinder for NCES, DoD Data Management Strategy and NetCentric IA
 In a microcosm, find the SOA implementation pitfalls and recommend
vector checks in specifications/developers guidance
• A Pillar of the overall DoD CIO investment strategy for DoD IT
 *next chart
• A Portfolio – not a program
 Began in January 2003
 Integration of functional components
 Not development of functional components
UNCLASSIFIED
Page 3
HF and the DoD CIO Strategic Investment Plan
FY04
FY 05
FY 06
FY07
FY08
Policy & Architecture Guidance
UCS Directive
UCS Implementation
Arch/NCOW Reference Model
Joint Tactical Radio System
Provides IP-based, self-managed,
BLOS, mobile data and voice
communications services
•Cluster
•Cluster
•Cluster
•Cluster
1 Vehicular & Army Rotary Wing
2 Handheld
IOC Cluster 2
AMF (Airborne, Maritime & Fixed Station)
5 Small form fit
IOC Cluster 5 Handheld/manpack ?
IOC Cluster AMF small
IOC Cluster 5 other form fits
IOC Cluster AMF large
?
•Optical Bandwidth to STEP and Teleport sites
•Optical Bandwidth to Ground Sites
FOC ( UP TO 101 Sites)
IOC ( 6 Sites)
TCA SATCOM
Wideband Gapfiller
1
•Optical IP Networking for Joint
Operations Centers and ISR locations
•Optical Bandwidth Support for
Additional Global Hawk UAVs
2
TSAT (CY11 Launch)
3
4
•Reachback Capabilities
for Deployed Forces
•Wideband Networking for UAVs and
Other ISR
Core Enterprise Services (9) + Application Program Interfaces
Net-Centric Enterprise Services
- Application
- Mediation
- User Assist
- Messaging
Increment 1 (All CESs) in 3 Spirals
- Enterprise Systems Management
- IA/Security
Defense in Depth
Information Assurance Programs
Arch
- Discovery
- Storage Services
FY10
- Collaboration
Identity Mgmt Infrastructure (PKI, Biometrics)
Increment 2 (All CESs) in 3 Spirals
FY13
Key Mgmt Infrastructure
Network Defense (Enterprise Sensor Grid)
Enables trusted computer, networking,
CAC Fully Deployed
1 Gb Terrestrial HAIPE IP
and data services to all GIG users
IA Component of GIG
10 Gb Optical Encryptor
10 Gb Terrestrial HAIPE IP
40 Gb Terrestrial
HAIPE IP
40 Gb Space HAIPE IP(FY10)
Op-Intel Data Applications Processes
Horizontal Fusion Portfolio
Develops and provides net-centric
means/tools to enable the smart pull
and fusion of data by users through
inter-related capability improvements
IOC Cluster 1
Optical Mesh IP Network
Provides ubiquitous, secure, robust
optical IP foundation network
Provides information and data
services to all GIG users
IPV6 Implementation Completed (Goal)
Software Communications Architecture
GIG Bandwidth Expansion
Incorporates mobile/tactical users and
global intelligence via optical cross
links and EHF IP links
FY09
- Improved Shared
- Collateral data available at RSCs & DECCs
Access to Collateral data
for Combat Support
- Improved Strategic & Tactical C2
- Automated Tagging
of Selected Sensor
and Combat Support
Data
- Collaborative Collection Management
- Deployment of web-enabled Collaborative Applications to Joint Commanders
- Net-centric Security Services
- Improved information Sharing with Coalition Partners
- Multi-INT Fusion for Warfighters
ISR Battle
Management
ForceNet
Net-Centric DCGS
Deployable CJTF HQs
Future Combat(examples)
SystemPage
(FCS)
UNCLASSIFIED
4
- Data Net-Centric
Enterprise Services
(DDMS)
2003/2004 Participants
UNCLASSIFIED
Page 5
2004 Accomplishments
•
•
•
Provided a web environment with search, discovery, collaboration, language
translation, etc…) for warfighters
Enabled web access to a myriad of data sources (person-based degree of
separation analysis, track data, NGA/NGIC/DIA data and products, weather,
HUMINT spot reports) meta-tagged with registration (I can find it) and security
tags (and match it to user clearance)
Created specifications and services supporting over 30 programs in a netcentric environment
 Provides the springboard for widespread net-centric operations and warfighting
•
•
Implemented a single sign-on for applications and data access for users
including coalition
Implemented a set of web-based security services that are more secure than
any available
 Ensures that users are exposed only to the data and services consistent with their
clearances
 First use of mobile code PKI signing hard cards on the SIPRNET
•
Proved that integration at the data level will save the DoD time and effort
 5 months start to finish to 30 projects
UNCLASSIFIED
Page 6
FY2003/04 Take Aways
• Implementation of a Net-centric environment is
technically doable
– Cultural and Policy issues make implementation difficult
• Net-Centric implementation is an integration effort
 Not about building “shiny objects”
– It’s about attaching capability to a common environment
 Focus is on interoperable services and accessible data
• We CAN capitalize on legacy investments
 Using web interfaces and tagging data
• Net-centric processes need continued investment and
refinement




Development
Test and Integration
Certification and Accreditation
User Operations (JFCOM)
UNCLASSIFIED
Page 7
Out in Front
HF deployment baseline is already in conformance with pending
Information Sharing Environment Legislation
• Proposed McCain/Lieberman Legislation inspired by 9/11 report
 Calls for an Information Sharing Network (Title II, Section 201)
– A “decentralized, distributed coordinated environment” which shares
“…information horizontally across agencies, vertically between levels of
government, and, as appropriate with the private sector” (Section 201(c)(2)(A),
page 201)
– “building on existing systems capabilities …” (Section 201(c)(2)(B), page
201)
– “utilizing industry best practices, … minimizing the centralization of data
and seeking to use common tools and capabilities whenever possible”
(Section 201(c)(2)(C), page 201)
– “employing an information rights management approach that controls
access to data rather than to whole networks” through “access controls,
authentication and authorization, audits, and other strong mechanisms”
(Section 201(c)(2)(D)&(I), page 201)
– “providing directory services for locating people and information… (Section
201(d)(1), page 202)
UNCLASSIFIED
Page 8
FY2005 Plan
• First user operational assessment of net-centric implementation
 FusionNet (18th Airborne) and JEODNet
– Operational Access to SOA Core Enterprise Services/Collateral Space
– FusionNet and JEODNet plug into Collateral Space as a Data Provider
and Consumer
• Pass lessons learned to cognizant organizations (DISA, NSA, …)
• Prepare for FY2006 activities
 Continue work on standards and specifications
– Identify implementation issues/forge path ahead
– Federation, Scalability, Security
– Incorporate next version of CES and new CES(es)
 Continue to bring in additional data sources and functional
capabilities into the environment (as funding allows)
UNCLASSIFIED
Page 9