1 / 37

usw-xml Next-Generation USW Interoperability using Extensible Markup Language (XML)

usw-xml Next-Generation USW Interoperability using Extensible Markup Language (XML) 18 October 2005. Don Brutzman Modeling, Virtual Environments & Simulation (MOVES) Institute Naval Postgraduate School (NPS) Monterey CA. Mike Grimley NAVSEA Warfare Centers - Newport Newport RI.

cgwendolyn
Download Presentation

usw-xml Next-Generation USW Interoperability using Extensible Markup Language (XML)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. usw-xml Next-Generation USW Interoperability using Extensible Markup Language (XML) 18 October 2005 Don Brutzman Modeling, Virtual Environments & Simulation (MOVES) Institute Naval Postgraduate School (NPS) Monterey CA Mike Grimley NAVSEA Warfare Centers - Newport Newport RI

  2. Background • Sponsored by NAVSEA PEO IWS for Undersea Warfare Decision Support System (USW-DSS), Fleet ASW Command for A-TAS, and others • Formed in order to support USW efforts to establish coherent battlespace visualization capabilities for network-centric undersea warfare • Creating a harmonized DON XML NDR compliant superset of existing USW tactical vocabularies

  3. Outline • Charter and motivation • Organize for success • usw-xml products • Project exemplars • Planning ahead

  4. Charter • The usw-xml working group is improving Undersea Warfare (USW) interoperability using Extensible Markup Language (XML) tagsets for system data interchange. • Cooperative collaboration between many stakeholders is needed to achieve good interoperability.

  5. Motivation • Many XML technical capabilities enable significantly improved capabilities for • USW system interoperability • Connecting legacy systems, diverse partners • USW Decision Support System, other projects • We expect this work to broadly benefit the Navy, industry and scientific community.

  6. How to connect already-built systems • Keep internal data model • Often can’t change internals easily anyway • Map to shared, external data model • Build data/message converters that wrap inputs/outputs of established/legacy system

  7. Motivation Currently

  8. Motivation Short term

  9. Motivation Long term 0 Translators/Stylesheets

  10. Process for creating common vocabulary • Develop a common view (and description) of the world. • What objects/classes exist in C3S world? • What properties do objects/classes have? • Agree on the representation of these objects. • obtw XML • Evaluate the data/information needs of your particular application/message. • Update model if necessary

  11. Archiving data is increasingly important • “Old” legacy programs not really maintainable • Past capabilities either repurposed or lost • Not a showstopper problem with source code, but collected data is collateral damage • Archiving data in well-structured, well-defined format keeps it accessible and usable • Even by programs that aren’t written yet

  12. Consistent messaging essential Consistent APIs feasible Human Systems Interoperability “stack” • Coalition • Joint • Battle group • Ship • System • Offboard robots

  13. Organizing for Success

  14. Sponsors • NAVSEA PEO IWS 5, Undersea Systems • USW Decision Support System (USW-DSS) program. • Carrier Tactical Support System (CVTSC) • Fleet ASW Command • Tactical Assessment Markup Language (TAML) for ASW Tactical Assessment System (A-TAS) • Other sponsors & participants are welcome. • Many programs represented by mail-list members • ASW C2 Requirements study lists ~18 candidates

  15. Participation • Forum for effective collaboration and shared effort • Voluntary contributions and dialog, mutually beneficial • Broad participation is welcome • Navy, Industry, Scientific community • U.S. military, civil service and defense contractors • Allied partners a future possibility, under review • Two levels of participation • Contributing participants, 1-2 teleconferences per week • Listeners: discussions on best practices, problem resolution, announcements of progress, new capabilities

  16. Mailing list Currently 96 members • Open subscription policy, moderated • Password protected (only distribute by voice) • Treat as For Official Use Only (FOUO) • Hosted by NPS on MOVES Institute server • mailto: usw-xml@MovesInstitute.org • List information: http://www.movesinstitute.org/mailman/listinfo/usw-xml • Email archives: http://www.movesinstitute.org/pipermail/usw-xml

  17. Website • Password protected (only distribute by voice) • Access control: For Official Use Only (FOUO) • Hosted by NPS on MOVES Institute server • http://web.nps.navy.mil/~brutzman/usw-xml.html • Project includes multiple web servers • support advanced XML server capabilities • support state-of-the-art technical experimentation • demonstrate exemplar configurations

  18. Website 2 • Calendar for events of common interest • Participating organizations and individuals are listed with contact information • SECRET server capabilities can be provided when needed

  19. Intellectual Property Rights (IPR) • Must be predeclared in order to enable effective group efforts • Otherwise long-running efforts might short circuit • Cannot afford tainting with IP/patent encumbrances • Participation requirement for Royalty Free (RF) use of any patented tech: • Follow guidelines of DoN CIO XML Working Group • Follow policy adopted from standards organizations (W3C, Web3D)

  20. Implementations and Open Source • Two implementations are usually needed to demonstrate interoperability • One version in open source is also usually a minimum requirement for interoperability • VRML-X3D experience • Commercial versions are OK, but not if a program is then “locked in” • because program becomes vulnerable, which is not in best interest of government (or industry)

  21. USW XML milestones 2004-2005 • Establish careful IPR policy • Issue call for resources (Spring 2004) • List XML schemas of interest • Comprehensive • What systems need what datasets/tagsets, including legacy systems without XML • Plan future at-sea exercise demonstrations

  22. USW XML milestones 2004-2005 • Solicited participation through briefs to DON BSC, C3S Developers Conference, and NDIA Conference • Compared tagsets of interest • C2IEDM compatibility judged feasible, next year • Used information requirements for ATAS – CVTSC communication as basis for usw-xml v1.0. (TAML) • Briefed members on ISO 11179 and ISO 15000 series specifications, which form the basis for the DON NDR. • Produced detailed comments on DON CIO XML Naming & Design Rules (NDR)

  23. Outreach • Connecting to multiple USW/ASW activities • Obviously we are already hard at work • usw-xml group welcomes specific participants to accept liaison responsibilities • Monitor other groups’ activities • Provide 2-way channel for information, action • Serve as group point of contact • Outreach is an ongoing activity

  24. References • Many! • Programs of record • XML, web services, specific tagsets • Best references of common interest are kept on website. Short summaries help. • Many resources support new efforts by building “path of least resistance”

  25. usw-xml Primary Product FY2005: TAML

  26. Tactical Assessment Markup Language (TAML) • Represents tactical track information, context • Consensus representation by group implementers • Supports multiple programs • ASW Tactical Assessment System (A-TAS) • USW Decision Support System (USW-DSS) • Carrier Tactical Support Center (CVTSC) • (Lots more system/community connections possible) • Integration, exemplar construction in progress • Web service already available from NUWC

  27. TAML schema excerpt

  28. TAML schema 2

  29. Sample TAML excerpt

  30. Planning ahead

  31. Project Goals 2006 • Determine what data & information is next • Participants assess what is important • Programs have interoperability requirements • CVTSC Data Models • Sonar is another good candidate • Continue to research, solicit and monitor existing vocabularies of interest to the usw-xml community. • Schemas currently used by DSS

  32. Project Goals 2006 (cont’d) • Consider integration of multiple tagsets • Componentized approach • Some may be non-Navy, e.g. SensorML • C2IEDM evaluation and harmonization • Ensure mapping between usw-xml and C2IEDM data models • Determine if any further maritime extensions are needed in the C2IEDM data model

  33. Weekly meeting • One hour meeting per week, each Tuesday • Time: 0700 Hawaii, 1000 pacific, 1300 eastern • Second meeting for developers each Friday • Audio bridge for call-in provided by NPS • Video teleconferencing (VTC) as well, when facilities and video bridge are available • NPS, NAVSEA DC. SPAWAR San Diego, Hawaii • Minutes posted to mailing list, kept online

  34. IITSEC 2005 • Interservice Interoperability for Training, Simulation and Education Conference • 28 November - 1 December, Orlando Florida • Weeklong demos of exemplar applications • Joint booth with NUWC Caruso team, NPS

  35. Conclusions • TAML 1.0 is a great shared asset • Tons of work already in progress • Where is the rest of the C4I community? • Collaborative approach is essential, since scope of technology & operational concepts is beyond any single player • Further scrutiny, participation and guidance are all welcome, we are “walking the walk.”

  36. Contact Don Brutzman brutzman@nps.navy.mil http://web.nps.navy.mil/~brutzman Code USW/Br, Naval Postgraduate School Monterey California 93943-5000 USA 1.831.656.2149 voice 1.831.656.7599 fax

  37. Contact Mike Grimley GrimleyMJ@Npt.NUWC.Navy.Mil DON CIO XML Working Group Liaison NAVSEA Warfare Centers - Newport Newport RI 1.401.832.2539 voice

More Related