1. IDEAS Core Model Concept
Exchanges are
via a commonly-agreed
IDEAS Core Model,
not translations
from point-to-point

2. Methodology and Approach
A foundation ontology based on set and meronymy theory
Membership
Spatio-temporal overlap
Domain ontology that is a specialization from the foundation
E.g., Agent, Process, Information Element
Reified relationships, e.g., whole-part for functional decomposition, overlap for input/output
Use of Business Objects Reference Ontology (BORO) methodology to clarify concepts
All concepts traced to real spatio-temporal examples
Participants continued to:
use UML as modeling language, profiled to IDEAS
derive model from agreed operational constructs
provide complete semantics
Participants will fully document all aspects of the model and methodology for the IDEAS capability
Participants will experiment with data exchange as they progress to ensure a model that can be implemented
The foundation forces rigor and enables “ontologic free lunch” wherein a pattern, once developed, is reusable for other domain representations.

3. high-level patterns (upper ontology) common objects (agreed taxonomy)
Structure
Layered approach
Starting from first principles to ensure common understanding at the most fundamental level
Reaching down to country-specific definitions whose meaning may need to be understood by other nations
fundamental concepts:
classes, instances, properties
foundation
high-level patterns (upper ontology)
commonly used relationships:
whole-part, sequence, etc.
common objects (agreed taxonomy)
internationally accepted terms:
person, organization, materiel, etc.
national
extension
national
extension
national
extension
national
extension
terminology specific to nations
that which may be useful to
other nations
- e.g. Bowman, Bradley FV, etc.

4. Foundation Top Level

5. Whole Part Pattern

6. Type Instance Pattern

7. Domain Level: Agent Super Sub Type

8. Process Whole-Part

9. Model Experimentation
First experiment, exchange architecture data regarding the processes, agents, information flows, and sequences of activities involved in Battlefield Human Casualty Management.
Using Canadian document as “test data”

10. Exchange Across Coalition Tools and Frameworks
SA XML Import
(Update logic)
EE XML Export (ALL)
Telelogic System Architect®
SQL Query
RDFS Database
IDEAS Data Exchange Format (RDFS)
IDEAS RDFS
Generate
Parse
*Many tools TBD; ones shown are notional

11. Exercise Concept
Identify a scenario where exchange of architecture planning data across the Coalition aids:
Planning for interoperability, e.g., processes, organizations, and/or systems
Identification of interoperability issues before they happen in a real operation
Better synchronization of forces in real operations