"[The] battlespace is complex and dynamic, requiring timely and clear decisions by all levels of military command. There is an unprecedented increase in the amount of data and information necessary to conduct operational planning and combat decision making. ...Information must flow quickly and seamlessly among...elements."

--Joint Technical Architecture (JTA) 
v2.0, 5/26/98, section 1

Ensure Data and Database Interoperability

More than 40 years ago, Eisenhower underscored the importance of joint operations as the key to future military victory. The combat engagements of the last 10 years have certainly borne this forecast out. "Jointness" has become a watchword of the services.
 
The move toward Jointness has exacerbated an already difficult information environment for battlefield commanders. Not only are the weapons systems of each of the services becoming increasingly complex and information-intensive, but combining them in a joint operation means all information elements must be coordinated. Unless this is done effectively, not only are individual units put at risk, but so is the eventual outcome of the military operation.
 
The Joint Technical Architecture (JTA) is an attempt to provide the overarching structure within which systems that meet the needs of present and future commanders can be implemented. One of the key tenants of the JTA is data and database interoperability.
 
Data and database interoperability addresses the format and meaning of data transferred between automated systems. The most obvious example of this data transfer is data passed via an electronic interface. Another example would be a database designed to be used by one or more automated systems.
 
The distinction made between data used internally and data that might be shared with other systems is significant. The classic focus of data and database interoperability has been interface data, data structures and elements designed for transfer between automated systems. While essential, this represents only a portion of the opportunities for seamless interoperability. Databases and data elements designed for internal use are often made available to other systems, either initially or later in their life cycle. When standard data elements are used, sharing of data becomes much easier and less error-prone.
 
Standard data elements also minimize the requirement for data translation software and reduce the potential for breakdowns in information transfer. Data element standardization reduces the cost, complexity, and overall level of resources expended on the development.
 
When developing a software system, the designer should strive to minimize the impact of database changes on other systems. Change to an application accessing a database should not force a change to any other application accessing the same database. Key characteristics such as database referential integrity, data transaction control, and database replication should be implemented by the database management system and not by application software. Relationships between data items should be defined based on queries made on the database. Data element names, definitions, minimum accuracy, data type, units of measure, and range of values should be defined to minimize the amount of translation required to share data with external systems.
 
Real-time systems pose a special problem for database management. The sophistication of the operational environment has spawned a wide variety of systems aimed to satisfy specific user needs. Mission success on the modern battlefield often requires that the systems be integrated. Not only do each of the systems have extensive database requirements, but the data they use often overlaps. When mission requirements mandate that this data exist in multiple locations, the risk to the system increases dramatically. Maintaining data consistency in this complex environment should rely on database management systems rather than applications software.

top

---