JPEO CBD Software Support Activity (Net-Centric Services ... · Software Support Activity...
Transcript of JPEO CBD Software Support Activity (Net-Centric Services ... · Software Support Activity...
Joint Program Executive Office for Chemical and Biological Defense
1
JPEO CBDJPEO CBD Software Support ActivitySoftware Support Activity
(Net(Net--Centric Services)Centric Services) January 9, 2007January 9, 2007
Kevin AdamsKevin AdamsChief, Future TechnologiesChief, Future Technologies
SSA DirectorSSA [email protected]@jpmis.mil
Joint Program Executive Office for Chemical and Biological Defense
2
Agenda
1. SSA Overview2. GIG and Net-Centric Issues
– C2 Transition to SOA– Migration Strategy
3. How Do We Meet the Challenge4. Leveraging Activities5. Road Ahead
Joint Program Executive Office for Chemical and Biological Defense
3
CBRN-SSA VisionJPEO-CBD
CBRNWARFIGHTERCAPABILITIES
Secure
Net-Accessible
Maintainable
Interoperable
Mission Composable
Joint
SoftwareSupportActivity(SSA)
JRO
PD TESS
JSTO
DISA
CJCSI/M
DoDD/I
JPM CA
JPM IS
JPM IP
JPM DC
JPM MS
JPM CP
JPM GN
JPM BD
SSA WORKS TO REALIZE THE VISION OF NET-CENTRIC WARFARE -Cost effective single point of contact for users (Customers, Developers, and Warfighters) to receive professional and timely assistance with all CBRN Defense program standards, interoperability, and supportability needs to ultimately facilitate the creation of more efficient, common, and consistently superior interoperable and integrated CBRN systems.
Joint Program Executive Office for Chemical and Biological Defense
4
S&T Transition
Standards & Policies
Integration & Test
(M&S,VV&A)Help Desk
JPEO-CBD JPM ISScott White
Architecture
JPEO-CBD SSA Project Director
Kevin Adams
JPEO-CBDMG Reeves
InformationAssurance
Data Management
LorRaine Duffy (Lead)Dan Reuben (Lead)CK Kwiatkowski (Lead)Tom Johnson (Chair)
Bill Snee (Lead)
Claude Speed (Lead) TBD (Lead)Jennifer Park (Lead, VV&A)
Staff Rep.Charles Anderson
Key:JPEO-CBD Staff
JPEO-CBD JPM IS JPEO-CBD SSAFunded By Other
Project SupportPeggy West
Chief Technical LeadJosh Pressnell
JPEO-CBD SSAProject Manager
Douglas HardyDep. Dick Brimson
Configuration ManagementQuality Assurance
Denise Milligan
Chief Systems EngineerDave Ferris
SSA FY07 Organization
Systems Engineer
Dave Ferris
Systems Engineer
Dave Ferris
CSE/CIODave Ferris/
Brenda Besore
Systems Engineer
Dave Ferris
Future AcquisitionCurt Wilhide
Future Acq Sys EngChristine
Crabill
Chief LogisticianGabe Patrico
JPEO SSA FA Stakeholder’s
Joint Program Executive Office for Chemical and Biological Defense
5
GIG Compliance– Compliance with the GIG means an information technology-based
initiative or an acquisition program, throughout its lifecycle:
– Meets the DoD Architecture Framework (DoDAF) requirements.
– Meets the Core Architecture Data Model (CADM) requirements for using/reusing architecture data.
– Meets the DoD Information Technology Standards Registry (DISR) requirements in selecting technologies and standards.
– Meets the DoD Net-Centric Data Strategy requirements and intent.
– Explicitly addresses net-centricity and determine the program's net- centric correspondence to key net-centric criteria (e.g., concepts, processes, services, technologies, standards, and taxonomy). (For further information see the Net-Centric Operations and Warfare Reference Model (NCOW RM) Compliance Assessment Methodology (Draft) - found on the GIG Architecture website).
– Meets the broad requirements set forth in the GIG Capstone Requirements Document.
Joint Program Executive Office for Chemical and Biological Defense
6
*NCOW RM
• The NCOW RM is focused on achieving net-centricity. Compliance with the NCOW RM translates to articulating how each program approaches and implements net-centric features. Compliance does not require separate documentation; rather, it requires that program managers and Sponsors/Domain Owners address, within existing architecture, analysis, and program architecture documentation, the issues identified by using the model, and further, that they make explicit the path to net-centricity the program is taking.
*Net-Centric Operational Warfare Reference Model
Joint Program Executive Office for Chemical and Biological Defense
7
SSA
JRO-CBRND
JPEO-CBD
R&D Labs/Industry
ECBC
DTRA (RN)
JSTO-CBD
IWMDTServices
S&T
ARCH
DM
I&T
HD
IA
S&P
DoDMDAPS
NCES
NECC
ABCS
FCS/SoSCOE
Constellation
ForceNet
8 JPEO-CBD
JPMs
CA/BD > JOAC/Holster LOE/PD TESSPM Guardian > Demo MS> MSAT ACTD >JROIP/CP/DECON > CB DATA
GIG/NCOW-RM
• RFP Language
• Metric Indicator
Net-Centric Interfacing Model
SOA Architectural Implementation
JWARN
JEM
JOEF
JBAIDS
Sensors
Etc……
Future Tech Framework
Common
Services
Plug and Play
Developer Toolkits and Frameworks
Support andCoordination
Test Frameworks
Joint Program Executive Office for Chemical and Biological Defense
8
Net-Centricity – What We Need to Know• Each of the Services are migrating to SOA
– ForceNet, FCS/SoSCOE, and Army Enterprise Architecture (AEA), Constellation NECC/NCES
• Enterprise Services are being defined – Data– Security– User interfacing standardization
• CBRN capabilities need to be modular and plug into various networks easily
– Plug and Play – Composeable – Scalable
• MDAP will drive the Architecture– C2 Systems will have open Architecture and Standards
Joint Program Executive Office for Chemical and Biological Defense
9
MDAP Integration
• Systems and Software Analysis, Architecture, Engineering, and Evaluation• Networking of Sensors and Systems• Distributed Web-Based Sensors• Net-centric computing and network algorithms• CBRN Sensor Emulation• C4ISR / C2• Data Modeling (CBRN Data Model and XML Schema)• Service Oriented Architectures• Expert Systems, Intelligent Agents, Distributed and Parallel Computing• Embedded systems• Real-Time Systems• Networked Communications (wireless and wired)• Modeling and Simulation (Expertise, Tools, Technology, Frameworks, Standards)• Information Assurance Planning, Strategies, Process, Policy and Execution, and
System Security Accreditations• Standards and Interfaces for Models, Information Systems, and Sensors
Will require expertise and understanding of the following:
Joint Program Executive Office for Chemical and Biological Defense
10
How Do We Meet the Challenge?
Joint Program Executive Office for Chemical and Biological Defense
11
Installations
HHQ / Strategic
Tactical Units (FCS)
CBRN Defense Capabilities Required at all Echelons and on all Platforms for Mission Effectiveness!
CBRN Defense Capabilities Required at all Echelons and on all Platforms for Mission Effectiveness!
Afloat (DDX)
Networked CBRN Net-
Centric COPs enabled by JPM
Information Systems, NCES
and NECC…
01100110011001100110011001100110011001100110011001100110
CBRN Warning,Reporting, Alerting,
Plans, Course of Action, CBRN
Status and Readiness
CBRN-EnabledGIG via
CBRN IS
GIG
Joint Integrated Modular Mission Configurable Networked CBRN Capabilities
CBRN Sensing
CBRN Medical Treatment
Integrated Warning and Reporting,
Hazard Prediction, Course of Action, and
Consequence Management
Individual Protection
Fixed, mobile, andplatform embeddedIntegrated sensing
capabilities
Pervasive CBRNNetworked Intel
Prophylaxis and triage
Continued CBRN- Protected
Individual Mission Execution
Integrated Protection for Installations,
Units, and Vehicles on the
move
Remove the threat, preserve the
Warfighter and the Equipment
Warfighter
Joint Program Executive Office for Chemical and Biological Defense
12
CBRN Data Model Supports Net-Centric Data Strategy
• Enables the grouping of services to create a system of systems• Defines common data elements when creating a web service• Used to make CBRN data discoverable and accessible• Eliminates point-to-point interface development• Used to Create the CBRN XML Schema• Reusable data definitions• Shortens System Development Time• Facilitates Reuse of System Components• Allows for investment in component improvement versus
component reinvention• Requires sustainment under POR purview
Joint Program Executive Office for Chemical and Biological Defense
13
Current S&T Efforts Supporting Common Services
• JSTO Sponsored Shared Common Operating Picture (COP) for HLS and HLD– Integrated shared COP capabilities for HLS/HLD
• Mostly message integration• JEM proxy
– Currently in phase 2• JSTO Sponsored Common CBRN Software Services
– A common framework to support Net-Centric Components and Services environments.
• NCES, NECC, SoSCOE, ForceNet e.g.• NECC & NCES pilots
– Awaiting Approval• Program risk reduction pilots and LOEs
– JCID on a Chip (JoaC)
– COE decoupling pilots– Technical decision pilots– Holster LOE (JPEO-CBD initiative)
Joint Program Executive Office for Chemical and Biological Defense
14
GIG (NCES, NECC, …)
IWMDT/CBRN Core
CBRN Tools CBRN Applications(JEM, JWARN, JOEF)
ESM
Operational Effects Environmental
Sensor Management Weapon Information Facility Information
DiscoveryCollaboration
StorageSecurity User Assistance
CBRN Modeling
Mediation
Messaging
GIG Applications
Application
CORE CBRN Services
Core Enterprise Services
GUI Toolkit
Security
GIS/Mapping
IWMDT/CBRN Enterprise FrameworkApplication Framework: GUI Framework
Core Services: Persistence/Database Messaging/Alerts
Portal/Portlets
Web Services
Interface Adapters Service OrchestrationRSS Publish/Subscribe
Database Synch/Replication System Monitors Load Balancers
Common application framework for
developing net- centric applications
Applications build to core services that isolate applications
from deployment environments
Proposed Leveraging Activities - Tech Base Architecture
Joint Program Executive Office for Chemical and Biological Defense
15
Provide CBRN products in a timely and efficient manner to the warfighter and first responder– Integrated family of products– Single integrated user interface to all services
Leveraging JPM IS Integrated Product Vision
Integration/Interoperability Path to NCES/JC2
JWARN
JEM
JOEF
CBR
N C
OI
Com
mon
Ser
vice
s
Phase 3 – Initial Integration
GU
IG
UI
JWARN
JEM
JOEF
CBR
N C
OI
Com
mon
Ser
vice
s
Phase4– Mature IntegrationPhase 1 – Pre-Interop
JWARN
JEM
Phase 2 – Initial Interop
JOEFG
UI
GU
IG
UI
JWARN
JEM
JOEF
GU
IG
UI
GU
I
GU
I
JPM IS Migration Vision
JPM IS UI Vision
JEM
JWARN*
JOEF*
COP/SituationalAwareness
GU
I
Portlets
Search Capabilities
Joint Program Executive Office for Chemical and Biological Defense
16
Maximize Re-Use at all Levels
JEM
Non-uniqueCBRNE
Capabilities
Presentation
Unique CBRNECapabilities
CustomInfrastructure
Interfaces
JWARN
Non-uniqueCBRNE
Capabilities
Presentation
Unique CBRNECapabilities
Custom Infrastructure
Interfaces
JOEF
Non-UniqueCBRNE
Capabilities
Presentation
Unique CBRNECapabilities
CustomInfrastructure
Interfaces
Independent
CBRN Framework
Common, ReusableCBRNE Services
Presentation
Common, ReusableInfrastructure
Services
JEM JWARN JOEF
Collaborative
(CBRN Data Model)
Any other CBRN Model
Joint Program Executive Office for Chemical and Biological Defense
17
Road Ahead for a Common CBRN Framework
• Review Message Sharing Requirements– Mediation service for Message conversion– Architecture for message converters and parsers
• Implement a Common GIS Framework– Same code base to; WebCOP, C2PC, Googlemaps, JWC.
• Put in Place an Open Architecture Approach to Integration– Allows decoupled messaging– Middleware agnostic– Insulation of program development cycles from others
• Open Architecture approach for Sensor Integration– Common front end to JWARN to allow multiple sensor networks
• Support Common Net-Centric Services
Joint Program Executive Office for Chemical and Biological Defense
18
SSA Goals • Need to reduce lifecycle cost of JPEO-CBD products
and artifacts as they relate to MDAP integration and interoperability.
• Increase collaboration and coordination in the CBRN development community.
• Maximize flexibility, reuse, and portability of software components.
• Reduce interfacing (outward looking) software for each POR.
• Align Tech Base under a SOA to transition to the user/warfighter product faster and cheaper.
Impacts SENSE/SHAPE/SHIELD/SUSTAIN
Joint Program Executive Office for Chemical and Biological Defense
19
BACKUPS
Joint Program Executive Office for Chemical and Biological Defense
20
JPM IS Migration Strategy Integration/Interoperability Path to FCS/NCES/NECC/Etc.
JWARN
JEM
JOEF
JOEF
JOEF
JWARNGU
IG
UI
Pre-Interoperability
JOEF
JEMJEMGU
I
JWARNGU
I
Initial Interoperability
JOEFGU
I
JEMJEMGU
I
datamodels
datamodels
datamodels
datamodels
datamodels data
JOEF
JEMJEMGU
I
JWARNGU
I
Initial Integration
JOEFGU
I
datamodels
datamodels
data
CB
RN
CO
ID
ata
Com
mon
Ser
vice
s
models
Mature Integration
datamodels
data
data
CB
RN
CO
ID
ata
Com
mon
Ser
vice
s
dataCBRN COIInformation Systems
dataCBRN COIInformation Systems
dataCBRN COIInformation Systems
CB
RN
HS
I -G
UI
COE 4.7 FCS/SoSCOE/NECC/NCES
models CBRN Dispersion and Transport Hazard Prediction Models
data Data Implementations Conforming to the CBRN COI Data Model
ARCHITECTURE MIGRATION STRATEGY - DISCIPLINED EVOLUTION OF DESIGN TO MEET THE VISION!
Phase 1 Phase 3Phase 2 Phase 4
Joint Program Executive Office for Chemical and Biological Defense
21
Joint CBRN Defense Functional Concept
• SENSE – The capability to continually provide the information about the CBRN situation at a time and place by detecting, identifying, and quantifying CBRN hazards in air, water, on land, on personnel, equipment or facilities. This capability includes detecting, identifying, and quantifying those CBRN hazards in all physical states (solid, liquid, gas).
• SHIELD –The capability to shield the force from harm caused by CBRN hazards by preventing or reducing individual and collective exposures, applying prophylaxis to prevent or mitigate negative physiological effects, and protecting critical equipment
• SUSTAIN – The ability to conduct decontamination and medical actions that enable the quick restoration of combat power, maintain/recover essential functions that are free from the effects of CBRN hazards, and facilitate the return to pre- incident operational capability as soon as possible.
• SHAPE – Provides the ability to characterize the CBRN hazard to the force commander - develop a clear understanding of the current and predicted CBRN situation; collect and assimilate info from sensors, intelligence, medical, etc., in near real time to inform personnel, provide actual and potential impacts of CBRN hazards; envision critical SENSE, SHIELD and SUSTAIN end states (preparation for operations); visualize the sequence of events that moves the force from its current state to those end states.
SHAPESHIELD
SENSE
SUST
AIN
Joint Program Executive Office for Chemical and Biological Defense
22
TO - BE
Comms
CoreEnterprise Services
(CES)
MessagingESM
Discovery Collaboration
Mediation Security
AppStorage
UserAsst
-
NNIRegistry
NGDS
NMWP SSO
ServiceRegistry
RegistryBrowser
MetadataRegistry
Messaging
Brokering Thick Clients
Portlets
Search
Thin Clients
ThreadedDisc.
Chat
FileSharing
SAML/WS-*
Identi
ty
Manag
emen
t
Service
Discove
ry
Mediat
ion
Secur
ity
User A
sst
Collaborat
ion
PKI
WhiteBoard
COICapabilities
GIS
QoS/SLA
Joint Program Executive Office for Chemical and Biological Defense
23
DoD Current Activities• GIS interoperability
– GIS applications availability via common open standards (OGC)• GIS targets
– FalconView, Joint WebCOP(JWC), OSWebCOP, Joint Battlespace Viewer (JBV), googleMap, GoogleEarth, C2PC
• COE migration to SOA’s– Messaging
• Using Exchange and outlook plugins from DMS program to bridge from COE to COTS
• Migrate off CMP and UCP
– Publish/Subscribe• Leveraging current GCCS-M initiatives like Joint translator forwarder(JXF).• Asynchronous messaging using JMS and the BEAWLS segments• RT Bridges - NDDS, OMG-DDS, SPLICE
– Registry/directory for lookups• Active Directory to LDAP configurations for finding services and enterprise
management of users and applications• NCES Service discovery and Service Registry (UDDI)
Joint Program Executive Office for Chemical and Biological Defense
24
IWMDT Software Architecture Layers
Client
EJB Container
Web Container
IWMDT JSP, HTML,
Javascript
App
licat
ion
Ser
vice
sS
ubsy
stem
S
ervi
ces
IWMDT Controller
IWMDT Actions
Pre
sent
atio
n S
ervi
ces
IWMDT Application
EJB
EJB Container
Database
BrowserWeb
Browser
Dat
a/M
odel
S
ervi
ces
BrowserExternal System
IWMDT Public Interface
Web
Ser
vice
s
DTRA Models (Scipuff, RIPDLIP,
SWFI, DWFI)
Subsystem EJB (Scenario, Weather,
CBFac, Plots)
Model/Data Interfaces