See Press Release for details of all finalists.
Register for real and virtual participation via: http://www.teamorlando.org/gametech/
FVWC - Federal Virtual Worlds Challenge
Name: Austin Tate (avatar: Ai Austin), with OpenVCE.net team: Jessica (Yun-Heh) Chen-Burger, Jeff Dalton, Stephen Potter, Gerhard Wickler
Product Description/Problem Statement: I-Room: a virtual space for intelligent interaction.
Rapidly creating and using a Virtual Operations Room for immersive training and for real missions. Outreach to geographically dispersed teams and agencies for input of their analysis skills. Robust and survivable alternatives to physical Operations Rooms. Demonstration shows examples of shared information access via the web (video feeds, weather screens, Twitter feed on nominated search tags), and team and personal task support (e.g. to do lists delivered from collaboration portal web site).
Location of Product: http://openvce.net/izone
Required Blog Page: http://fvwc-iroom.blogspot.com/
Benefit of Virtual World Chosen: Second Life is an openly accessible virtual world with many elements suited to collaboration. It can be used freely with instant registration and access for new users and can provide publicly accessible areas for work across institutions. Opensim is open source and is compatible with the Second Life viewer. It is not as scalable a platform at this stage as Second Life, but it offers richer collaborative and media facilities, as well as the capability to be self hosted to run behind firewalls.
Visit an I-Room now in Second Life [if you do not yet have a Second Life avatar Join here]:
Watch videos of an I-Room in use:
Example I-Rooms for Training, Simulation and Tutorials
I-Rooms are available in Second Life and Opensim. An I-Room provides a two storey building with central area and four work zones, designed for collaborative and brain storming style meetings. An I-Room can be used an a rapidly deployed operations center for example. Plenty of wall space is available for displays and gadgets. Each of the four corners can easily be converted to a small two storey block, or a larger double height block. The I-Room style buildings are used in the I-X/I-Room research on intelligent collaborative and task support environments at AIAI, The University of Edinburgh.
An example I-Room in use for the "Whole of Society Crises Response" (WoSCR) Community is available for demonstration, to show the public what is being created, and to seek feedback from potential government users. The I-Room 3D buildling model and all technical facilities within the virtual worlds and on suporting web sites is available as open soirce assets and software. Demonstrations for new applications can be created using the OpenVCE.net facilities and the Vue and VCE regions in Second Life.
Technical web site: http://www.aiai.ed.ac.uk/project/i-room/
Caption: Link ups between real meeting spaces and a unified interaction space in a Virtual World I-Room.
Caption: I-Zone in use within the Open Virtual Collaboration Environment (OpenVCE.net).
Caption: Various sized I-Rooms are available with a core plus four corner modules design.
The demonstration shows visitors what can be done through an I-Room even though the demonstration area is set up for specific uses and experiments for the "Whole of Society Crises Response" (WoSCR) community. This is done by having a greeter I-Robot offer NEW callers a web link back to this page and an in-world notecard. A possible tailored demonstration could be set up in a spare I-Room elsewhere if needed, but having an active room will better demonstrate what one would look like when populated with status and information feed displays.
A tailored I-Room may include active support for a standard operating procedure (SOP) for establishing a virtual ops center for example - using the ideas and the existing I-X domain models from work with USJFCOM's Joint Personnel Recovery Agency (JPRA) Personnel Recovery Education and Training Center (PRETC) - but augmented to allow someone to obtain, install and set up the I-X end services and the in-world elements for connecting to services, twitter feeds and information like weather imagery and map feeds... something that uses what everyone will know and understand as necessary for a new ops center... to make a new ops center for a mission or to respond to an event. An I-Room can also be tailored to give out users' task lists and status of where users are in the execution of a joint process or plan. This can be used for effective meeting support where team members may not all be on-line at once.
A radar could trigger the display of a page (with <I-N-C-A> task and activity orientated information on it) by avatar name and would be an example of something we might then do properly with the I-Room helper and I-X linked to SOPs and to do lists stored on a web collaboration portal like OpenVCE.net.
Some of the commands for the I-X helper agent running within the "Polycom Phone" in the I-Room are listed at http://openvce.net/iroom-helper
A sample <I-N-C-A> style "to do" list page at http://openvce.net/todo-fvwc-example
Experiments with the use of "Shared Media" enabled by the Second Life Viewer 2.0 Beta for more effective collaboration in the I-Room is underway. See examples of some experimentation described at http://openvce.net/sl-viewer-2-shared-media-demos
The I-Room Helper Robot provides a centralised mechanism by which users can access the facilities that the I-Room offers them. It also can be linked to an external I-X agent that allows instructions to be sent to it from an I-X Process Panel (or any other I-X agent). In their basic form, an interaction with the Robot takes the form of an activity name (a verb) and then any appropriate parameters. For instance, instructing the Robot to say hello causes the Robot to announce "hello" on the Second Life open chat channel. It is intended that the functonality of the Robot - in terms of the messages it 'understands', that is, to which it can respond usefully - would be extended as appropriate for specific applications. This might involve modifications to the Robot's code (written in LSL, the Linden Scripting Language) or additions to the Robot's "I-Room Setup Notecard" to associate additional capabilities (verbs) with objects.
We assume that the Robot has been configured and placed in the I-Room, and has been switched on. The basic manner in which users interact with the Robot is by chatting with it on a designated channel. By default this is channel 9 (and this is the value we will use here in examples) but this can be altered by changing the value of the channel variable in the Robot's I-Room Help script.
The Robot responds to the following standard commands that are 'chatted' by avatars on its designated channel (ie, prefix the command with /9 if using the default channel). Alternatively, if communicating with the Robot from I-X, the appropriate message (without channel information) should be sent as an I-X activity to the I-X Second Life agent (from a Process Panel activities can be easily constructed and sent with the Tools > Messenger tool).
Commands may be give via channel 9 (by default) to the helper in-world. I.e. /9 command
A summary of the commands is here:
Furthermore, it should be noted that many of the activities listed above involve the Robot saying something on one or other of the Second Life chat channels. Hence, this effectively constrains the in-world size of the I-Room to the radius within which chat is audible, which is currently 20 metres; all objects and participating avatars should lie within this radius.
Information is at http://openvce.net/iroom. Much more detail, in the context of an application to a product team support meeting space and a Scotch Whisky tasting tutorial room application is at http://www.aiai.ed.ac.uk/project/i-room/