Key Work Elements

1. Demonstration of Machine-Translation tools in Arabic
2. Demonstration of collaborative tools appropriate for civil-military support
3. Demonstration of remote communications capabilities appropriate for both civilian and military use within an austere environment
4. Demonstrate a proposed Information Zone capability.
5. Demonstrate Logistics support through collaborative tools defined for Iraq
6. Demonstrate iterative Humanitarian Assessment collection and analysis on world-standard indicators
7. Demonstrate simultaneous and collaborative GIS functionality across at least three nations.
8. Demonstrate open-source application effectiveness for micro-entrepreneurship.
9. Demonstrate resilient, robust, and sustainable techniques for remote habitation
10. Demonstrate a responsive collaborative framework for disaster response.

_______________________________________________________________________________________________

Tasks demonstrating the Key Work Elements:

Translation:

1. Two topics will be chosen by 10am daily from Arabic current events and evaluated using eTAP-Arabic to gather and filter key facts and new information.  Key results will be presented as a newsletter each evening by 6 PM. (Scored by DARPA for cost / benefit analysis, and the critical value of the reports).
2. Daily evaluation of two relevant video clips in translation from the eTAP-XL Video Monitoring System. The translated clips will be reviewed for utility by a CPA translator, a native speaker, and the NVTC, to be completed by 5pm. (Scored for response time, and ability to meet specific the translation needs of site users)
3. Submission of two daily items in Arabic from the al Jazeera live-feed on-site to a native speaker/cultural advisor (NS-CA) and to the National Virtual Translation Center (NVTC) for content and meaning. (NVTC scored on comparison to NS/CA as a gold standard and for turnaround time)
4. Publication from the SA site of an electronic DARPA Tides Iraq Reconstruction Report daily, and a DARPA-TIDES Global Threat Update at least once, during the period 17-22 July.
5. Demonstrate daily use of a multi-lingual, pre-recorded, speech-cued, phrase-based and hand-held interview system. The system will be used by non-specialists for humanitarian assessment interviews in Portuguese, Russian, Arabic, Pashto, Dari, and Tagalog (Scored for ease of use, ability to start and complete tasks, and the task completion time)
6. Use of Arabic / English two-way, real-time, secure, multi-lingual chat capability, with both text and video, used on a daily basis. (Scored for an ability to discover and communicate critical specific information, clarification of dialog, and ease-of-use)

Collaboration:

7. Collect two HA forms into a Zope database daily 17-22 July using paper to HTML to Groove with smart pulling of the appropriate Zope/Plone site, all through the SA site. Confirm automatic distributed receipt in the mainland US, the UK, Italy, and Baghdad, both civil society and military.
8. Collect two different HA forms into a Zope/Plone database using paper to browser form, to Zope/Plone, with smart pulling of the appropriate Groove workspace, all through the SA site. Confirm automatic distributed receipt in the mainland US, the UK, Italy, and Baghdad, both civil society and military.
9. Push and pull both photos and videos using an HP iPaq PocketPC and Groove File Sharing. Confirm automatic distributed receipt in the mainland US, the UK, Italy, and Baghdad, both civil society and military.
10. Confirm conversation with two US military, two international military, two civil-society, and two unrelated civilians each day from the SA site.
11. From the SA site pose questions, and receive answers, from three remote specialists each day 17-22 July. Questions should be multi-modal with text, audio, and images incorporated as appropriate.
12. From the SA site, speak daily with at least three remote participants using secure VOIP.
13. From the SA site, converse daily at least three remote participants using secure video.
14. From the SA site, daily annotate a map collaboratively noting (a) the route taken most recently by the Pony Express, (b) the unsecure wireless access clouds found along that route, and (c) the number of red cars seen along the route and where.
15. From the SA site, distribute a calendar showing the annotated events of the day to site participants within three countries.
16. From a remote (non-SA) site build a Groove workspace library of maps, documents, and files updated throughout the participant community daily. Include information from the New York Times, the Early Bird, the D-TIRR, the DT-GTU, a local paper, the Congressional Quarterly, the Colorado Legislature, and the Australian Parliament.
17. From a remote site build a Groove reference library of policies, procedures, publications, maps, and images relevant to humanitarian support. Ensure viewers are present for all file types, and ensure all files types are present to be viewed.
18. From a remote site build a Professional Contacts form and populate it with all participants within Strong Angel. Ensure Boolean searches can be done on all fields. Ensure the Plone forms and the Groove forms perform identically and are visible to each other through Zope entries.
19. From a remote site, extract and plot the positions of all participants whose "Current Work" coordinates are present within the Professional Contacts rolodex.
20. From a remote site, prepare forms for travel logistics and track the arrivals and departures of participants and guests though an automatic calendar feed. Use a standard travel form from a major travel service.
21. From a remote site prepare a collaborative shipping form and track the passage of goods to and from the SA site. Use one of the standardized international transport logistics forms from the United Nations Joint Logistics Center in Rome.
22. From the SA site determine four Island sites and four remote sites (plus the SA site) for participation in an Emergency Intercom system using Groove secure VOIP as designed for the Al Rashid hotel in Baghdad. Monitor those nine sites 24x7 within the SA site.
23. Establish comms every four hours with remote sites across global time zones and devise a protocol for checking in with keyword alerts.
24. Establish work-hour comms with all local Island participants using keyword alerts.
25. Establish ongoing chat during working hours with Baghdad, CENTCOM-Tampa, Washington DC, and San Diego.
26. Establish ongoing secure VOIP instant messaging with at least four sites across the world, sending a daily annotated jpg from the SA site in a simultaneous file transfer with the voice description.
27. Receive daily from the Hawaii County Law Enforcement and EMS a log of the previous 24 hours, describing events of import to the SA effort.
28. Plot an accumulating GIS overlay of the events from law enforcement and EMS.
29. Demonstrate open-source interactive tele-journalism software for reporting from low-bandwidth, high-interest areas.
    
30. Demonstrate a Mediated Collaboration session using complementary collaboration systems.
31. Broadcast a secure video stream of several yurt areas to remote civilians unrelated to either civil society or the US government. Have each of them use a screen-capture mode with event reporting to the Strong Angel Pacific Region Coordinator.
32. Publish a managed blog of thoughts, events, and impressions updated through the day, with global submissions.
33. There will be a single machine where events at the site can be watched and coordinated. This will be centralized viewpoint for situational awareness. It will be capable of, but not necessarily for, command or control.

Communications:

34. Establish data comms between all systems within the SA site.
35. Establish RF comms between the six handheld radios.
36. Establish a radio protocol, with physical management, call signs, and security procedures.
37. Establish a bi-directional voice link from radio to laptop to a remote land-line phone.
38. Establish a self-sustaining 802.11 cloud within and around a parked vehicle.
39. Establish a self-sustaining mobile relay server for Groove within a vehicle, accessible through the 802.11 cloud.
40. Synchronize five separate Groove spaces using a portable relay server for a remote and disconnected Groove workspace member not otherwise accessible (e.g. from a member located within the Waipio Valley).
41. Show a Groove satellite internet update through a two-leg, 20-mile Line-of-Sight relay for an 802.11b generated by a remote vehicle.(update from the MedWeb satellite while parked at, for example, the Wiamea airport.)
42. Receive an update on a location of a colleague in the field though a GPS radio signal displayed on another radio in the field.
43. Plot the location of deployed SA field staff, with confirmation through the GIS overlay in Washington and Baghdad.
44. Demonstrate the resilience of the Panasonic Toughbook laptops under very adverse conditions (beach sand, salt, wind, tropical sun, dropping from a vehicle onto pavement), Bury in sand overnight. Play DVDs the following day.
45.  Engage the global ham radio community in information sharing through data and voice, confirming the passing of messages to at least three continents.
46. Drive the Pony Express vehicle to a remote area with no connectivity. Establish an 802.11 cloud and a point-to-point relay access to a participant within the SA site. Send and receive an Instant Message 200 feet from the vehicle.
47. Establish a Pony Express cloud in two separate and disconnected locations. Synch a unique Groove workspace shared only between those two sites. (e.g. Waipio and Laupahoehoe)
48. Establish a Pony Express cloud and sync Groove between unrelated civil and military sites sharing a unique workspace (e.g. Waimea EMS and the US Army's Pohakuloa Training Area)
49. Demonstrate at least one system that meets all DoD Directive 8100.2 criteria for secure and reliable wireless communications. We will use that system to focus on smart-pull all the way to the farthest-forward users (including those usually disconnected) on a secure and trusted global grid, using multiple classes of systems (edge- and center-based) for the sharing of secure GIS overlays to localize items of interest through a collaborative, distributed information space.
    

Assessment Analysis on Standardized Indicators:

50. Define one perspective for the optimal indicators needed to evaluate post-conflict reconstruction in Iraq.
51. Determine which of those indicators are available for direct assessment (vs. calculated from aggregates elsewhere)
52. Develop forms for the collection of those available indicators.
53. Develop a Zope database for collection of completed indicator assessments.
54. Develop an open-source reporting method for displaying the current indicator collection status
55. Develop an open-source reporting method for the actual indicator status.
56. Collect on those forms each day, filling the database, testing the reporting tools, iterating as necessary. Make accessible to OSD, with iteration driven by OSD requirements.
57. Record the presence and speech of people presenting at the Strong Angel site with information for us in other languages. Submit those recordings (both audio and video) for later evaluation by translators, ensuring that information from those “at the gate” who need to speak with us is captured and reviewed for value.

GIS:

58. Plot all handheld Garmin Rino GPS radio signals in a Groove space visible in Washington DC in real-time.
59. Plot all events reported from EMS and Hawaii County law enforcement daily, and do so on a Groove system visible within at least three locations.
60. Plot all humanitarian assessments with metadata links embedded within defined and standard humanitarian GIS symbology.
61. Provide collaborative satellite maps with six-layer overlays from open sources (layers to be determined by current events).

• Email
• Calendar
• Documents
• Spreadsheets
• Presentations
• Databases
• GIS from database information
• Database reporting
• Open source medical information reporting
• Web-based collaboration
• Instant messaging
• VOIP
• Web browsing
• PDF creation
• Application programming in any flavor of C

63. Demonstrate the presence of educational materials for training on each capability.
64. Provide for distribution a brief paper on the value of an entrepreneurial engine in software having no license fees, no royalties, no legal obligations to non-indigenous corporations, and yet the ability to develop expertise locally for tackling development and reconstruction goals.
65. Connect with five sites working (at that point) with no one on Groove. Describe the download and task integration for Groove from the web, then accomplish an instant message from the new (remote) site to the SA site using VOIP and a file transfer.

Habitation:

66. Develop a site from empty land to effective habitation with global communication within four hours. Prove with VOIP, video chat, file sharing, and the submission of a completed humanitarian assessment form to three remote sites off-Island.
67. Establish habitation using techniques capable of leaving no trace after dismantling.
68. Establish lighting, communication, security, and power using only renewable, non-polluting energy up to 1000 watts per hour per day, 24x7 (may be supplemented).
69. Demonstrate the resilience of a distributed energy architecture. Make explicit the political, psychosocial, and economic sense found in stabilizing a restive population through reliable energy decentralization and consequent resilience, particularly in light of persistent and recurrent sabotage on more brittle centralized energy distribution.
70. Establish storage and habitation using small, simple, robust and flexible shelters specialized for population support in disasters and each costing less than $500 and weighing less than 100 lbs. (Dymax Emergency Shelters from the Buckminster Fuller Institute)
71. Establish workspace and habitation using large, culturally neutral, robust and flexible shelters specialized as coordination centers in disaster response and each costing less than $2000 and weighing less than 200 lbs. (Geodesic Yurts from Shelter-Systems, near Stanford University).
72. Establish a site-produced badge capability with photos and color-coding for access.

Implementation

73. Develop a single DVD with the final Groove, Zope, Plone, and GIS architecture, including professional contacts, all forms, the reference library, and all required educational materials, within 7 days after the completion of SA-II. The DVD will be designed for immediate utility in the event of a disaster response requiring similar capabilities.
74. Develop an implementation architecture and process capable of absorbing this suite of capabilities within an organization.

Community:

75. Receive an entirely new suggestion from a member of the local community. Capture it on tape, distribute it to two sectoral experts, and receive feedback from those experts within 24 hours. Contact the community member with the thoughts born of that suggestion.
76. Contact family members from two SA staff daily, with exchange of text, audio, and images, both synchronous and asynchronous.
77. Accept, acknowledge, and inform participants about a gift from the community.
78. Demonstrate site evaluations by uninvolved local community members of SA projects and capabilities, with questionnaire evidence from those community members that they understood a substantial portion of the activities within the Strong Angel site.
79. Demonstrate non-harmful, pro-social conduct to local children.
80. Contact SA ethical guides daily to ensure mission focus and appropriate conduct.
81. Test Strong Angel educational material with local schoolteachers.
82. Establish a method for interacting with the press effectively, including twice-daily briefings and frequent personal interview time.
83. Each day one member of the SA staff will disappear for 6 hours; staff member chosen at random by low-number draw. No access, no accountability, and no fixed return time. (Location will be known by two members of the SA staff and one member of local law enforcement).

END