Use or disclosure of data contained on this page is subject to the restriction on the cover page of this presentation. Instrumentation Hardware Abstraction Language (IHAL) Demonstration Knowledge Based Systems, Inc. College Station, Texas L-3 Telemetry East AFFTC – Edwards AFB Distribution authorized to U.S. Government Agencies only, as the data is PROPRIETARY (See sec. 5.6 of DoD SBIR solicitation). Other requests for release shall be referred to AFFTC/XPR. SBIR Data Rights Contract No.FA C-0012 Contractor NameKnowledge Based Systems, Inc. Contractor Address1408 University Drive East, College Station, TX Expiration of SBIR Data Rights PeriodFive (5) years from contract completion date. The Government's rights to use, modify, reproduce, release, perform, display, or disclose technical data or computer software marked with this legend are restricted during the period shown as provided in paragraph (b)(4) of the Rights in Noncommercial Technical Data and Computer Software - Small Business Innovative Research (SBIR) Program clause contained in the above identified contract. No restrictions apply after the expiration date shown above. Any reproduction of technical data, computer software, or portions thereof marked with this legend must also reproduce the markings. This document contains information exempt from mandatory disclosure under the FOIA. Exemption 4 applies. ©2009 Knowledge Based Systems, Inc.

Use or disclosure of data contained on this page is subject to the restriction on the cover page of this presentation. The Problem Hardware Component 1 ISS 1 Hardware Component 4 Hardware Component n Hardware Component 2 ISS m ISS 3 ISS 2 Hardware Component 3... N x M Translations Vendor-Specific Hardware Representations Diverse ISS Development Environments Version Management Vendor-Proprietary Configuration Rules

Use or disclosure of data contained on this page is subject to the restriction on the cover page of this presentation. The Solution Hardware Component 1 ISS 1 Hardware Component 4 Hardware Component n Hardware Component 2 ISS m ISS 3 ISS 2 Hardware Component 3 IHAL... N + M Translations Vendor Neutral XML- Based Ease of Integration Proprietary Rules not exposed

Use or disclosure of data contained on this page is subject to the restriction on the cover page of this presentation. IHAL Key Features Instrumentation Hardware Abstraction Language Comprehensive representation and integration of instruments, cards and transducers –IHAL represents instruments (DAUs, network devices, etc.), cards (signal conditioners, bus interface modules, PCM encoders, multiplexers, etc) and transducers (pressure sensors, strain gauges, etc.) in a consistent manner. Vendor neutral –IHAL includes generic representations that can be translated to / from vendor-specific internal representations. Standards-based –XML-based representation is a well-establish standard for representing structured data.

Use or disclosure of data contained on this page is subject to the restriction on the cover page of this presentation. IHAL Key Features (con't) Supports hardware capability descriptions –IHAL “pool” features represent device descriptions at the level found in marketing or engineering datasheets. Supports current configuration descriptions –IHAL “use” features represent the realized network (multiple instances of the same device identified by serial number) and the connection among the device instances, as well as the configuration of each instance. Extensible –The IHAL schema can be easily extended to represent vendor specific concepts (i.e., proprietary bus types) and arbitrary name- value pairs to support vendor applications. Component-based –The IHAL schema is designed in such a way as to allow users to use only what they need for their application

Use or disclosure of data contained on this page is subject to the restriction on the cover page of this presentation. IHAL Benefits Enables complete instrumentation hardware descriptions Consistent modeling framework –Functional decomposition Broad representation –Represents instruments, transducers, connections, pool data and instance data Vendor-independent automated reasoning –A vendor-independent language is needed to do automated, cross-vendor reasoning

Use or disclosure of data contained on this page is subject to the restriction on the cover page of this presentation. Protecting Proprietary Rules Need to protect vendor proprietary configuration rules E.g. Setting parameter X affects the available values for parameter Y. Define a standard API for configuring hardware settings When user attempts to set a value: Make call to vendor’s implementation of API Vendor returns the “impact” Which settings changed? Which settings now have restricted values?

Use or disclosure of data contained on this page is subject to the restriction on the cover page of this presentation. Vendor Proprietary Software (Multiple Vendors) Standards - based Software Open Standards IHAL Configuration API Vision Hardware Programming Configuration logic Instrumentation Visualization Instrumentation Selection Instrumentation Configuration Hardware Programming Configuration logic

Use or disclosure of data contained on this page is subject to the restriction on the cover page of this presentation. API Request configuration IHAL Hardware Tree IHAL configuration change IHAL Impact Vision Standards - based Software Instrumentation Visualization Instrumentation Selection Instrumentation Configuration Vendor Proprietary Software (Multiple Vendors) Hardware Programming Rules for parameter setting Hardware Programming Rules for parameter setting Configuration Logic

Use or disclosure of data contained on this page is subject to the restriction on the cover page of this presentation. Vendor Proprietary Software Standards – Based Software Open Standards IHAL Configuration API InstrumentMap L-3 Vista TEC Demonstration

Use or disclosure of data contained on this page is subject to the restriction on the cover page of this presentation. Standards – Based Software Vendor Proprietary Software Web Service (REST over HTTP) InstrumentMap L-3 Vista TEC Request configuration IHAL Hardware Tree IHAL configuration change IHAL Impact Demonstration Conforms to IHAL Configuration API Specification

Use or disclosure of data contained on this page is subject to the restriction on the cover page of this presentation. Benefits Supports multi-vendor hardware configuration from single user interface Vendor-neutral, standards-based method of storing and representing hardware configurations Vendor-neutral, standards-based method of configuring hardware Does not require exposure of proprietary configuration logic

Use or disclosure of data contained on this page is subject to the restriction on the cover page of this presentation. Points of Contact L-3 Joe Sulewski EAFB –Charles Jones –Dalphana Bowman KBSI –John Hamilton –Timothy Darr –Ronald Fernandes