Common CBRN Sensor Interface (CCSI)

(1)

May 7, 2009

Advance Planning Briefing for Industry

(APBI)

Common CBRN Sensor Interface

(CCSI)

David Ferris

Chief Systems Engineer

JPEO CBD

(2)

Purpose

• Describe the JPEO CBD Common CBRN Sensor

Interface (CCSI)

–

Why

–

What It Is

–

Why It Is Important

• CBD Enterprise

• Impact on Industry partners

–

Next Steps

2

(3)

Why CCSI?

• A standard way to communicate

–

All JPEO-CBD developed CBRN Sensors will interface using a

published standard sensor interface

• An interoperability guarantee

–

All JPEO-CBD developed applications will be able to implement

to the standard and guarantee interoperability between sensors

and information systems

• A net-centric direction

–

All JPEO-CBD sensors can be available via CCSI enabled

web-services

A Standard supporting these key tenets for the

entire CBRN community of interest (COI)

(4)

What is CCSI?

• A set of standards for CBRN Sensors

–

Volume I – Summary and Architecture

• Contains goals, concepts, sensor characteristics

• States and Modes, DoDAF Architecture Products

• Sensor Development and Certification Process

–

Volume II – Physical Interface Standards

• Sensor specifics separated by size

–

Small/Personal Sensor requirements

–

Large Sensor requirement

–

Volume III – Software Interface Standards

• Performance requirements

• Application Layer Protocol

• XML Schema Definitions

• Application Program Interface (API)

• CCSI Compliance Test Tools

–

Sensor Schema Validation

–

Communications Validation

4

(5)

Cradle

CCSI Block Diagram

Host

Platform

Host System

Information

Systems

Host

Platform

Host System

Information

Systems

Host

Platform

Host System

Information

Systems

Sensor

Base Sensor

Power

Distribution

& Interface

Logic (PDIL)

Control

Component

(CC)

Sensing

Component

(SC)

Dismounted

Power

Component

(DPC)

Wireless

Comms

Component

(WCC)

User

Interface

Component

(UIC)

CCSI API

Network

CCSI Application Layer

Protocol

CCSI Application Layer

Protocol

(6)

14_090507_CCSI_APBI

6 What CCSI Looks Like

Yellow – CCSI Standardized

Blue – Platform Controlled

Red – Sensor Vendor

(7)

CCSI Software

• Sensors are defined by vendors using a standard XML

Schema

–

Common elements, commands, structures

–

Sensor unique elements, commands, structures

• Single communications method using a standard XML

Schema

–

Used on all communication transports

–

Messaging details include common and sensor unique items

• Sensor Definition XML and CCSI schemas maintained in

repositories

A host application can identify and communicate with

any CCSI sensor using common commands and reports.

(8)

Where We Are Now

• CCSI Published – 15 Feb 2008

–

Posted on the JPEO-CBD public web site (http://www.jpeocbd.osd.mil)

–

Incorporating standard in appropriate solicitations

• Working Next CCSI Revision

–

Initial implementations lessons learned

–

Preparing FedBizOps announcement to solicit industry inputs

• CCSI implemented (in the exhibit area)

–

AN/UDR-14 with CCSI embedded

–

M4 JCAD CCSI Compliant Communications Adapter

• CCSI on-going implementations

–

OGC SWE through a Sensor Interface Service (SIS) (video in the exhibit

area)

–

STIRS JCTD

–

FCS Sensor Mounting Cradles (example in exhibit area)

8

(9)

High-Level CBD Concept

How our Systems Fit Together

(10)

CBRN Tactical Layer SV-4

Several Ongoing Initiatives to Synchronize & Simplify the Enterprise

10 P1

Prov ide CBRN

Information

Management

Serv ices

P4

Perform CBRN

Health Serv ices

Support

P9

Perform

Decontamination

P10

Prov ide E xternal

Communications

P13

Pre-Position

CBRN Assets

P12

Perform CBRN

Mission

Planning

P3

Perform CBRNE

Sensor

Operations

P5

Prov ide

Collectiv e

Protection

P6

Prov ide

Indiv idual

Protection

P7

Enable

Continuity of

Operations

P8

Perform

Sampling

Net-Centri c Security and Discovery Services (NSDS) External Systems Higher HQ

Tactical Data Flow (SV-04 Data Flow) System Architect Tue Jan 20, 2009 Status Operational Direction Operational Direction Status Status Authorization_to_Communi cate Request_Communication Authorization_to_Communi cate Request_Communication Recon Plans CP Plans Decon Plans Planning Direction Diagnosis Sample CBRNE Detection Treatment Authorization CBRNE Detection MOPP Order

Coll ecti ve Protection Order Operational Direction Sample Decon Information Alerts Tactical Situation Sensor Commands Barrier Integrity Mapping Data Sensor Data

14_090507_CCSI_APBI

(11)

Where CCSI Fits

P1

Prov ide CBRN

Information

Management

Serv ices

P4

Perform CBRN

Health Serv ices

Support

P9

Perform

Decontamination

P10

Prov ide E xternal

Communications

P13

Pre-Position

CBRN Assets

P12

Perform CBRN

Mission

Planning

P3

Perform CBRNE

Sensor

Operations

P5

Prov ide

Collectiv e

Protection

P6

Prov ide

Indiv idual

Protection

P7

Enable

Continuity of

Operations

P8

Perform

Sampling

Net-Centri c Security and Discovery Higher HQ

Tactical Data Flow (SV-04 Data Flow) System Architect Tue Jan 20, 2009 Status Operational Direction Operational Direction Status Status Authorization_to_Communi cate Request_Communication Recon Plans CP Plans Decon Plans Planning Direction Diagnosis Sample CBRNE Detection Treatment Authorization CBRNE Detection MOPP Order

Coll ecti ve Protection Order Operational Direction Sample Decon Information Alerts Tactical Situation Sensor Commands Barrier Integrity Mapping Data Sensor Data