TECHNOLOGY AREAS: Information Systems, Battlespace, Human Systems

ACQUISITION PROGRAM: Battle Force Tactical Trainer ACAT IV

The technology within this topic is restricted under the International Traffic in Arms Regulation (ITAR), which controls the export and import of defense-related material and services. Offerors must disclose any proposed use of foreign nationals, their country of origin, and what tasks each would accomplish in the statement of work in accordance with section 3.5.b.(7) of the solicitation.

OBJECTIVE: To develop a highly usable data model/process that prepends self-identifying information to a datagram and provides the ability to make intelligent decisions with regard to restrictions, purpose, and applicability of the data content. The key development consideration is to have the "insertable" service available to any application development environment and servers that are development environment insensitive so that regardless of what development tools are used to encode the service into the system, the server can properly administer the appropriate management, administrative, policy and controls.

DESCRIPTION: The problem: There exists no single framework and support software services or applications with processing servers to prepend highly configurable standardized tags to an information message or datagram which allows a system to automatically identify target audience using intelligence based rules.

This becomes a design handicap when attempting to develop widely Open Systems Architecture.
PEO IWS 7C is soliciting proposal for developing a data tagging model, common framework for datagram segregation, programming language independent services that can be applied directly to developing applications and servers capable of directing or restricting information flow based on any compliant application generate datagram.

The following consideration must be directly addressed in the solution space so that an implementation of the framework is highly practice:
Multi Level Security,
Safety Permission to Train,
Secure voice and non-secure voice
Live versus simulated versus virtual versus constructive entities,
Tactical versus, Maintenance versus Engineering versus Navigation versus Damage Control
versus locally owned and generated data [Own ship] versus remotely created data [multi-ship].
USN Forces vice Joint and Coalition Forces.

This Open System Architecture approach to datagram segregation must at a minimum comply with OA Navy Standards for hardware, as required, and identify the methodology for software development and be re-usable as an architecture design for other Navy engineering requirements, including NET-CENTRIC and Coalition Warfare paradigms.

The use of self identifying datagrams provides the control information tagging necessary for targeted distribution and filtering of information to a specific recipient, only when appropriate. When applied to the surface training domain, this developed technology will provide the capability to target data information delivery and maintain the necessary restriction and control without using hardware based services such as switches, routers, bridges, guards and gateways. This technology, once developed, will likely not replace the physical security requirements for separation often implemented with Guards or Gateways, however, it may be a complimentary application layer to achieve physical security cooperative identification violation indicator further fortifying the Guard or Gateway.

PHASE I: Develop, using available DoD CADM compliant development tools, a model and architecture that is representative of the necessary data model/structure, service add-in for applications and application independent servers. The deliverable shall clearly identify a control authority programmable taxonomy, such as an XML Namespace, and a programmable hierarchy of restriction, for classification and restriction purposes and how they integrate, interoperate and disseminate information as prescribed. The deliverables must also identify a strategy to practically deliver these developing technologies into a serviceable system component.

Develop a concept of operation for implementation into the TSTS Event Driven Architecture (EDA) and Service Oriented Architecture (SOA) services paradigm. It is highly recommended that CANES be well understood as a potential NAVSEA foundational implementation of SOA.

PHASE II: Develop a non-scripted demonstrable prototype. The prototype shall be able to perform the rudimentary control authority programmable taxonomy configuration and application of tagging to datagrams. The prototype shall also include a non-scripted capability to achieve hierarchy designation as applied to classification restriction indicators. The final component of the prototype shall be a server demonstration showing how information control, restriction and directed delivery was achieved.

Complete the engineering development documentation compliant with industry best practices to be negotiated with IWS 7C and CADM compliant.

Prepare, in collaboration with IWS 7C, a set of acceptance criteria, including parameters for source, purpose, restriction, and constraints for the prototype demonstration.

Complete the necessary documentation, including requirements and specification, to allow for a successful Phase III implementation.

PHASE III: If the contractor successfully passes the acceptance criteria during the Phase II demonstration, it is anticipated that the contractor will be awarded a Phase III contract to perform the full scale development of the technology components, as a System Integrator, for their solution within the TSTS development team under the integration guidance of the PEO IWS 7C.

Private Sector Commercial Potential/Dual-Use Applications
The contractor is free to apply this broad schema to the vast number of commercial application that requires similar data segregation and/or control.

REFERENCE:
HLA IEEE Specification 1516 see section on data distribution management system

KEYWORDS: Multilevel security; datagram; object identifiers; data tagging; data models; data distribution management system;

TPOC: Peter Chu
Phone: (202)781-1992
Fax:
Email: [email protected]

** TOPIC AUTHOR (TPOC) **

DoD Notice:   Between November 13 and December 9, 2007, you may talk directly with the Topic Author(s) to ask technical questions about the topics. Their contact information is listed above. For reasons of competitive fairness, direct communication between proposers and topic authors is not allowed starting December 10, 2007, when DoD begins accepting proposals for this solicitation.

However, proposers may still submit written questions about solicitation topics through the DoD's SBIR/STTR Interactive Topic Information System (SITIS), in which the questioner and respondent remain anonymous and all questions and answers are posted electronically for general viewing until the solicitation closes. All proposers are advised to monitor SITIS (08.1 Q&A) during the solicitation period for questions and answers, and other significant information, relevant to the SBIR 08.1 topic under which they are proposing.

If you have general questions about DoD SBIR program, please contact the DoD SBIR Help Desk at (866) 724-7457 or email weblink.