Chem-Bio Defense Quarterly
The Common CBRN Interface
BECOMES A REALITY
By Claude Speed and Tom Swanson, JPEO-CBD Software Support Activity (SSA) Architecture team CCSI is one piece within a suite of Common Components, illustrated below. These components will provide a standardized interface for all CBRN sensors, from the physical interface through sensor security and discovery. The Net-Centric Security and Discovery Service (NSDS) provides: • Authentication services to ensure that sensors and applications are authorized to communicate • Registry services to enable applications to find sensors that will support their operational requirements.
T
he Common CBRN Sensor Interface (CCSI) standard represents a step forward in the realization of MG Reeves’ concept of modular sensing capabilities that implement standardized interfaces. CCSI is the JPEO-CBD standard for sensor physical and electronic interfaces, including component interconnects, power, external connectors, eXtensible Markup Language (XML) communications, a standard basic command set, and modularity. It will support net-centric communications for all JPEO-CBD sensors and enable host platforms to identify and communicate with any CCSI sensor using common commands and reports.
0
Jan - Mar 008
JPEO-CBD
The Common Modular Communications Interface Standard defines: • Standard Ethernet communications • Standard wireless communications. The CCSI Standard provides: • Common sensor interface performance requirements • Required and recommended standards • Recommendations for sensor architecture and implementation • An evolving standard as technology changes, lessons are learned, etc. CCSI is one of the first of the JPEO-CBD Common Components. It is a standard -- not a program . It will be retrofit into existing programs where it makes sense to satisfy warfighter requirements. CCSI does not specify sensing capability, power consumption of sensors, or size and weight for all sensors. It also does not specify host system data processing since that is controlled by Service and joint doctrine, approved requirements, and program-specific needs. CCSI Development was initiated after the Joint CBRN Dismounted Reconnaissance System (JCDRS) Phase III Limited Objective Experiment (LOE), generally known as the Holster Concept. Holster continues as experimentation on miniaturization, new environments, new sensors, and communications methods. CCSI was spun out to be the first set of common sensor specifications for JPEO-CBD. CCSI was a collaborative effort among JPEO-CBD and outside interested parties, including: • JPEO-CBD Software Support Activity (SSA) • JPEO-CBD Future Acquisitions (FA) • JPEO-CBD Joint Project Manager for Biological Defense (JPM BD) • JPEO-CBD Joint Project Manager for Nuclear, Biological and Chemical Contamination Avoidance (JPM NBC CA) • JPEO-CBD Joint Project Manager for Information Systems (JPM IS) • Defense Threat Reduction Agency (DTRA) Joint Science and Technology Office (JSTO) • Joint Requirements Office (JRO) • Penn State University • Northrop Grumman Information Technology JCID developers • Industry at appropriate points in the review and comment period on the draft standard. Initial Development of the CCSI began with a characterization of CBRN Sensors to identify common attributes that were candidates for standardization, such as: • Sensor Installation (Fixed, mobile, dismounted, etc.) • Sensor Power (Commercial, platform, internal, etc.) • Sensor Communications (Wired, wireless, none, bandwidth needs, etc.) • Sensor Operation (Interactive, automatic, mixed) • Sensor Environments (Combat, severe, outdoor, indoor) • Sensor Security (High, medium, low for physical, commuwww.jpeocbd.osd.mil
nications, electronic) This information was used to develop DoD Architecture Framework (DoDAF) architecture products such as the Operational Activity Model (OV-5), the Operational Information Exchange Matrix (OV-3), the logical data model (OV-7) and the XML schema (SV-11). The SSA Architecture Team determined that network security and discovery mechanisms would be scoped to another architecture (NSDS) to enable the CCSI to operate interchangeably in environments such as the System of Systems Common operational Environment (SOSCOE) of the Future Combat Systems (FCS), the Defense Information Systems Agency’s (DISA) Net-Centric Enterprise Services (NCES), and Naval Engineering Control Systems (ECS). The CCSI Standard includes: • CCSI Volume I – Summary and Architecture • CCSI Volume II – Physical Interface Standards • CCSI Volume III – Electronic Interface Standards CCSI Implementation is well underway. The CCSI Standard was completed in November 2007 and provides the information needed for: • Vendors to embed all required CCSI capabilities into their sensors during its development • A third party to develop components for use by many vendors, e.g. Joint Tactical Radio System (JTRS) radio and Global Positioning System (GPS) receiver components, dismounted power components • Software for CCSI as a package for vendors to use As part of implementation, components and sensors will be tested to ensure that they are CCSI-compliant and registered. CCSI Test Tools will be provided to vendors from a public repository to validate the Sensor Definition XML and sensor communications. This Standard is referenced by the JPEO-CBD Net-Centric Implementation Policy and will be included in all future JPEO-CBD program procurements to ensure that the JPEOCBD net-centric vision is fully realized.
1