“New” things Discussed in London Detailed planning for 4/08 demo Backtrack rehearsals, setups, … “Military Utility” Ops planning and data exchange scenario Useful results from exchange (ideas on later slide) Documentation Op Concept Doc AU started Model description Methodology (Data TWG could use too) Training on implementing data exchange (e.g., for federates, vendors) Model telecon’s between trips

1. Demo Preliminary Plan

2. Military Utility Contrast “as-is” way that Coalition Ops Planning is done with “to-be” Need to show relevant to procedures, tools, methods, … planners would actually use May not look like classic “architecture”

“As-is” We need to document how the Coalition Ops Planning scenario would be done today Manual? (paper, email, faxes, phone calls, meetings, …) Discovery of issues in the field (on-the-job interoperability)

“To-Be” Military Utility Scenario Visualization Environment Decision Environment “To-Be” Military Utility Scenario Relational DB Query Environment SQL Query OWL/RDFS DB Data Mining Environment RDFS Database IDEAS Data Exchange Format (RDFS)

Plan Mock-up some CA-US casualty mgmt process comparison displays (started): Highlight different processes, sequences, information flows, event triggers* Maybe side-by-side Post on IDEAS FTP site for review US review with Joint Forces Command Once OK, see what tool gets us close *truly different, names assumed aligned or mapped

3. Documentation Need some preliminary documentation available at conference

Need to revisit scope and structure IDEAS OCD Current structure: CAPABILITY IDENTIFICATION DEFINITION AND REFERENCE DOCUMENT SOLUTION INDEPENDENT CAPABILITY NEEDS EXISTING COALITION PLANNING SYSTEM SYSTEM SOLUTION DESCRIPTION Mostly TBS/TBD Need to revisit scope and structure

NOT EA-generated document; rather key information IDEAS Model (prelim) Sections for each layer: Foundation Common Patterns Domain Within each: For each package/diagram: Narrative description, diagram walkthru and items of special note Standard data dictionary information Examples NOT EA-generated document; rather key information

IDEAS Methodology (prelim) How IDEAS differs from other methodologies, e.g., “view from nowhere” approach BORO Methodology Set Theory The Naming Pattern Incremental Experimentation BORO overview “Sausage grinders”: Walk thru diagram Examples

IDEAS Usage Guide OWL/RDFS Specification Walk thru Special notes Examples Guidance from experimentation on: Generation from tools and databases Ingestion into tools and databases i.e., “lessons learned” Querying and “data mining”

4. Bi-weekly telecons More modeling, less stausing Track “critical path” issues for 4/08 demo and make sure management team is well aware of Track team action items