Registration Travel claim $50 needed for XMSF breaks Thanks to many of you for letting us make $150 needed for MOVES open house breaks reservations, despite SATO ticket hassles Government rates saves us a bunch of money I Rachel Davis is handling registration details Cecelia Childers will provide forms to fill out. Telephone for messages: +1.831.656.1126 Please save your receipts Cecelia is in MOVES lab Spanagel 256.x3818 Thanks one and all for cheerful professionals Wireless networking Handouts 802.11B provided XMSF workshop folder MOVES open-house brochure Web3D Consortium's X3D SDK CD VES open-house DVD Outgoing mail server. mail.nps. navy.-mi MOVES open house highlights MOVES lab Spanagel 286 Dico. if heeded,in settings ors d oeuvres ThursdaymorningAmenicasarmy.com cation domains Discrete-event and constructive Virtual worlds and continuous simulations Multi-agent systerms Further technical discussion Interactive, man-in-the-loop, equipmerit-in-loop systems Live and virtual entities, mixed seamlessly Distance leaming fo ong participants 中p u Teaching and training Ity vIa reach? Be ciear what
4 19-20 August 2002 19 Registration $50 needed for XMSF breaks $150 needed for MOVES open house breaks Rachel Davis is handling registration details. Telephone for messages: +1.831.656.1126 Thanks one and all for cheerful professionalism! 19-20 August 2002 20 Travel claims Thanks to many of you for letting us make reservations, despite SATO ticket hassles. Government rates saves us a bunch of money. Cecelia Childers will provide forms to fill out. Please save your receipts! Cecelia is in MOVES lab Spanagel 256, x3818 n mailto:cmchilde@nps.navy.mil 19-20 August 2002 21 Wireless networking 802.11B provided n SSID: campus n WEP key: hex: cafebabeee $ cafebabeee 0xcafebabeee n DHCP: yes Outgoing mail server: mail.nps.navy.mil Ethernet connections also available if needed, in MOVES lab Spanagel 286. DHCP settings. 19-20 August 2002 22 Handouts XMSF workshop folder MOVES open-house brochure Web3D Consortium’s X3D SDK CDs MOVES open-house DVD MOVES open house highlights n Tuesday afternoon: our web-based work, reception nWednesday evening: demos in lab, hors d’oeuvres n Thursday morning: AmericasArmy.com 19-20 August 2002 23 Further technical discussion 19-20 August 2002 24 Application Domains Discrete-event and constructive simulations Virtual worlds and continuous simulations Multi-agent systems Interactive, man-in-the-loop, equipment-in-loop systems Live and virtual entities, mixed seamlessly Distance learning for interaction among participants n Audio and video (both needed for WAN testing anyway) n Multiformat whiteboard; recording and playback n Teaching and training compatibility via ADL SCORM n Maybe inclusion is too far a reach? Be clear what is/isn’t
Top-Level Requirements 1 Top-Level Requirements 2 Compatible with Web architecture and technologies Modular a Highly distributed Use by humans and software agents equally important Ability to directly Su using XML Integrate with tacti Connection point between syntax and RDFISchema, semantics Iife-cydle pattems, Top-Level Requirements 3 Top-Level Requirements 4 Support for XML and multiple p ically extensible at run Small, fast, computing (distr buted operating systems) redundancy, etc. Expected network performance: Modems through ADSL (0. 05.-1.5 Mbps) far limited participe 10-1Gbps for Public library of w oc3 up through gig Cross-platform capabilitie Backward compatibility with existing architectures and endenng support anc simulations otocols, where if makes ser SP M&S Functional Requirements M ssue Backward abilit Authoritative represent Composability Multi-resolution modeling (TA), htinxllwweLita. ltsidisa.mi Simulation support services Time managemen Discuss approaches for playback capture. Logging and play years), likely (3-5 ye
5 19-20 August 2002 25 Top-Level Requirements 1 Ability to interact directly and scalably over the network Compatible with Web architecture and technologies n Highly distributed Use by humans and software agents equally important Support for composable, reusable model components n Root data-structure representations specified using XML schema n Representations in other languages autogenerated directly n Connection point between syntax and RDF Schema, semantics 19-20 August 2002 26 Top-Level Requirements 2 Simple learning curve and repeatable examples n Support users and developers Modular structure n Ability to directly interact with network layer n Plug-ins connecting into kernel plug-ins at run time Standards-based n IEEE, ISO, W3C, IETF, Web3D Integrate with tactical systems n Augment group shared picture of operations n Producers and consumers n System life-cycle patterns, repeatability 19-20 August 2002 27 Top-Level Requirements 3 Support for XML and multiple programming languages Dynamically extensible at run time: “always on” n software + hardware, diversity includes backwards compatibility n loose coupling, verification/validation, repair, graceful degradation, redundancy, etc. Security levels consistent with current Web technology Public library of useful reusable components Cross-platform capabilities Rendering support and architectural hooks for visual simulations 19-20 August 2002 28 Top-Level Requirements 4 Expected computer performance: n Small, fast, inexpensive computers n Reconnect via GRID computing (distributed operating systems) Expected network performance: n Modems through ADSL (0.05-1.5 Mbps) for limited participation n 10 - 1Gbps for local participation n OC3 up through gigabit wide-area networking Backward compatibility with existing architectures and protocols, where it makes sense n e.g. DIS, HLA/RTI, ALSP, probably many others 19-20 August 2002 29 M&S Functional Requirements Backward compatibility Authoritative representations Composability Multi-resolution modeling Tactical system integration Simulation support services n Time management n Logging and playback 19-20 August 2002 30 M&S Issues Discuss the shared goal of bringing working M&S applications matching real world problems into tactical use. Discuss approaches for backwards compatibility to HLA/RTI and DIS technologies which don’t constrain emergence of new capabilities. Explore specific bridging approaches for HLA/RTI and DIS over web channels. Discuss compatibility with the Joint Technical Architecture (JTA), http://www-jta.itsi.disa.mil. Explore integration of C4I systems to augment joint common operational picture. Discuss approaches for playback capture. Identify technology availability: immediate, near-term (1-2 years), likely (3-5 years), problematic
Design ldeas 1 Design Ideas ervices support wide-area routing and playback ming metaphors+ XMl tagsets/registries all Language and object-syste -level time ab ing languages and AP bdet anguage bindings Infrastructur da Wire protocols bly defined using XML Run-time extensibity. portability, interoper/ability for bility from Schema Business Model 1 Business Model 2 Roval fee. us able wuthout ahy fee rell Commercial models in partnership with open-source important to ha Int Offer nning ski for a fee and give up ngt a Proprietary softwar Long-term stable business intrastructure. they can use any license they like of this and se r - Someone needs to put together the simulations Even t al the parts 中 中四 Success of the overall endeavor is key to business success DoD Business Model Open Issues Commercial tech is crucial We can't do it alone Special technology requirements harmful anslate into alw g too much for unique, Nothing succeeds like sucdess ndards and industrly best practices makes best sense for industry partners aton. or 3 upporting inherent 6
6 19-20 August 2002 31 Design Ideas 1 Object-oriented programs + validatable structured data n Repeatable programming metaphors + XML tagsets/registries Language and object-system independent n e.g. CORBA/IDL, SOAP, RMI/RPC, others Design patterns unambiguously define language bindings n Map representations, component models from root XML schemas to programming languages and API bindings of interest Wire protocols unambiguously, flexibly defined using XML n Run-time extensibility, portability, interoperability for streams n Packet description language -or- direct mappability from Schema 19-20 August 2002 32 Design Ideas 2 Time services support wide-area routing and playback n Participating computer clocks all set correctly(!) via NTP or GPS n RTP for all stream headers n SMIL for stream synchronization n Higher-level time abstractions communicable by system n What about supercomputer batch-mode asynchronous? Infrastructure represented as objects in system n Enable object and service discovery at runtime n Ability to monitor, test, improve systems at local and global scale 19-20 August 2002 33 Business Model 1 Minimal architecture is open source implementation n Royalty free, usable without any fee restrictions whatsoever Important to have two or more interoperable implementations n Commercial implementations profitably augment open source Long-term stable infrastructure enables sustainable business models n Flexible architecture broadens market: not “just” military simulation, also full World Wide Web via open/secure Internets n Web-enabled architecture allows more sponsors to participate, which allows simulations, models, and applications to survive despite intermittent funding profiles n Transferable career-building skills and reusable experience for programmers and managers 19-20 August 2002 34 Business Model 2 Commercial models in partnership with open-source n Support w Offer programming skill for a fee and give up rights to the source if it is infrastructure related. n Proprietary software w A vendor may write a simulator that runs on top of the free infrastructure. They can use any license they like on this and sell it as they see fit. n Consulting w Someone needs to put together the simulations. Even if all the parts are free, this is a salable service. n Maintenance w Numerous success stories exist. Success of the overall endeavor is key to business success. 19-20 August 2002 35 DoD Business Model Commercial technology is crucial nWe can’t do it alone Special technology requirements harmful n Translate into always spending too much for unique, outdated technology Nothing succeeds like success n Slipstreaming standards and industry “best practices” makes best sense for industry partners too 19-20 August 2002 36 Open Issues Source code control n Interoperability test suite and certification shows conformance n Source forking no longer divisive issue, let many flowers bloom n “Actual results” validation through use with tactical systems Architecture n What are good driving exemplar applications? wReality pulls teams through the big design space wMust show significant “value add” to current practices plus current excitement n Can we extend some existing systems (e.g. HLA/RTI capable), show interoperability with legacy systems via good examples? we.g. NSS, OneSAF, ITEM n Multiple inheritance – no; multiple interfaces – yes n Do we need a specified method for distributed synchronization, or is open architecture supporting different models sufficient?
Recent work: workshop software componentization Contact mature and wel defined f building exemplar Slidesets and Contacts Rooms 31.6562305 Jeb/XML Root 200B(by Don's office) 1538 Networking: Spanagel 254(by Mikes office) Katherine Morse 88266728 858-826-4407 M+S: Right here in auditor http://www.movesinstituTe.org/xmsf
7 19-20 August 2002 37 Recent work: workshop on software componentization July 2002, DMSO, DC Consensus seemed to be: n components are a worthwhile approach to consider for improving composability and interoperability of diverse interacting simulations n component technology is sufficiently mature and well defined for building exemplars Slidesets and conclusions available? _____ 19-20 August 2002 38 Contact 19-20 August 2002 39 Contacts Don Brutzman brutzman@nps.navy.mil 831.656.2149 Michael Zyda zyda@nps.navy.mil 831.656.2305 Don McGregor mcgredo@nps.navy.mil 831.656.4090 Andrzej Kapolka akapolk@nps.navy.mil 831.656.2253 Mark Pullen mpullen@gmu.edu 703.993.1538 Katherine Morse morsek@saic.com 858.826.6728 Steve Fouskarinis steven.fouskarinis@saic.com 858-826-4407 http://www.MovesInstitute.org/xmsf 19-20 August 2002 40 Rooms Web/XML: Root 200B (by Don’s office) Networking: Spanagel 254 (by Mike’s office) M + S: Right here in auditorium
Intentionally blank
Intentionally blank