Common CBRN Sensor Interface (CCSI) May 7, 2009 Advance Planning Briefing for Industry (APBI) David Ferris Chief Systems Engineer JPEO CBD david.ferris@jpeocbd.osd.mil (703) 681-0813
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
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 webservices A Standard supporting these key tenets for the entire CBRN community of interest (COI) 3
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 Joint Program Executive Office for Chemical and Biological Defense CCSI Block Diagram Host Host System System Host System Information Information Systems Information Systems Systems Host Host Platform Host Platform Platform Cradle CCSI API Power Distribution & Interface Logic (PDIL) Dismounted Power Component (DPC) CCSI API Sensing Component (SC) Network CCSI Application Layer Protocol Control Component (CC) Base Sensor CCSI Application Layer Protocol Wireless Comms Component (WCC) User Interface Component (UIC) Sensor
What CCSI Looks Like Legend Yellow CCSI Standardized Blue Platform Controlled Red Sensor Vendor 6
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. 7
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 Joint Program Executive Office for Chemical and Biological Defense High-Level CBD Concept How our Systems Fit Together
CBRN Tactical Layer SV-4 Several Ongoing Initiatives to Synchronize & Simplify the Enterprise Barrier Integrity CBRNE Detection P9 Perform Decontamination P8 Perform Sampling Decon Information Sample P3 Perform CBRNE Sensor Operations CBRNE Detection Operational Direction Mapping Data P7 Enable Continuity of Operations Higher HQ Planning Direction P12 Perform CBRN Mission Planning Sensor Commands Status Sample Treatment Authorization P1 Prov ide CBRN Information Management Serv ices MOPP Order Collective Protection Order Sensor Data Tactical Situation P6 Prov ide Indiv idual Protection Decon Plans Operational Direction Recon Plans CP Plans P13 Pre-Position CBRN Assets Status P5 Prov ide Collectiv e Protection Tactical Data Flow (SV-04 Data Flow) System Architect Tue Jan 20, 2009 P4 Perform CBRN Health Serv ices Support Diagnosis Alerts Status P10 Prov ide External Communications Request_Communication Authorization_to_Communicate 10 Operational Direction Net-Centric Security and External Systems Request_Communication Discovery Services (NSDS) Authorization_to_Communicate
Where CCSI Fits Barrier Integrity CBRNE Detection P9 Perform Decontamination P8 Perform Sampling Decon Information Sample Higher HQ Planning Direction P12 Perform CBRN Mission Planning P3 Perform CBRNE Sensor Operations CBRNE Detection Sensor Commands Status Sample Treatment Authorization Operational Direction Mapping Data P1 Prov ide CBRN Information Management Serv ices MOPP Order Collective Protection Order P7 Enable Continuity of Operations Sensor Data Tactical Situation P6 Prov ide Indiv idual Protection Decon Plans Operational Direction Recon Plans CP Plans P13 Pre-Position CBRN Assets Status P5 Prov ide Collectiv e Protection Common CCBRN Sensor Interface (CCSI) Impact Tactical Data Flow (SV-04 Data Flow) System Architect Tue Jan 20, 2009 P4 Perform CBRN Health Serv ices Support Diagnosis Alerts 11 Status P10 Prov ide External Communications Request_Communication Authorization_to_Communicate Operational Direction Net-Centric Security and External Systems Request_Communication Discovery Services (NSDS) Authorization_to_Communicate
Next Steps Validate & Refine Software reference implementation in the C language currently in-development Will be provided to industry for use/comment when complete Refine and validate connector/mount for all environments Soliciting Industry input for next revision FebBizOps and other industry announcements will contain specifics CCSI Working Group Finalize lifecycle management plan Initiate process to migrate appropriate portions of CCSI to an Industry Standard Software Interface aspects XML Schema & Validation 12
13 Joint Program Executive Office for Chemical and Biological Defense The Result
Questions? David L. Ferris, Jr. Chief Systems Engineer Joint PEO for Chem-Bio Defense david.ferris@jpeocbd.osd.mil (703)681-0813 14